Pay attention at getsentry/team-mobile#11 (comment)
I guess getsentry/team-mobile#11 should be implemented in order to fix this correctly otherwise those checks based on the handled flag also have side effects.

Pay attention at getsentry/team-mobile#11 (comment) I guess getsentry/team-mobile#11 should be implemented in order to fix this correctly otherwise those checks based on the handled flag also have side effects.

I have tried to use the SentryEnvelope to read the byte array generated by the SDK.

EnvelopeReader reader = new EnvelopeReader(options.getSerializer());
InputStream targetStream = new ByteArrayInputStream(envelope.getBytes(Charset.forName("UTF-8")));
SentryEnvelope javaEnvelope = reader.read(targetStream);
hub.captureEnvelope(javaEnvelope);

The envelope was captured but now the envelope is different from the previously ones, for example:

• tags: missing isSideLoaded, os.rooted.
• Missing App Build, ID, Name, Start Time, Version, Permissions
• Missing user.id
• OS: Different fields

https://sentry.io/organizations/sentry-sdks/issues/3268302122/events/507506e2637e4bd69616965ffd5cd079/?project=5522756

https://sentry.io/organizations/sentry-sdks/issues/3268302122/events/28d12291411b40738d4ad475b846207f/?project=5522756#context-app

@lucas-zimerman the event is enriched with device context after its being written in the disk (by a file observer), that's how it works on Android and it should not, that's the reason about getsentry/team-mobile#11

hi,guys, I am using sentry-cordova and have sometimes double breadcrubms, can we do something with that ? I do not see similar fix for sentry-cordova project