Mischan Toosarani-Hausberger

Thx for verifying, @mntt-SSE; that is what I expected. `LocalDumps` bypasses application-local handling in favor of a centralized dump approach. It should be possible to deactivate it for your application...

> And each entry has a `DumpFolder` key with the data `%PROGRAMDATA%\NVIDIA Corporation\CrashDumps`. All of them are the same, and none seem to point to the application I'm using, and...

For further root-causing, it would certainly help if you could also gather the debug output of the Native SDK on the systems where the dump happens in `%LOCALAPPDATA%\CrashDumps`; maybe something...

> I tried attaching WinDbg to crashpad_handler.exe but I don't seem to get any logging from it in the Logs widget. Do I have to build it with a certain...

> Ah, sorry, here is what's being printed on startup from a computer that doesn't work (which is the same as when it works): Okay, the logs are wrapped, interleaved,...

There is currently no transport transactionality of events. If an event ends up in the send queue and the transport cannot send for whatever reason, the event is lost. If...

Btw since you use `crashpad`, implementing a custom transport will not help you with adding delivery guarantees for crashes since the `crashpad_handler` uses its own transport.

As I answered in the other issue, binary releases can make sense for Windows. Still, they would have to reflect all the combinations of backend, shared/static sentry, and shared/static runtime...

> 1: I guess tags are missing when using breakpad, because the minidumps are sent by breakpad itself, rather via the Android SDK which enriches the envelopes, right? It is...

> I'm curious to know whether this issue is unique to our project, or if the compatibility between breakpad and Android is not supported by design. This issue is not...