Usecase

A customer would want to collect user feedback for a crash. They are trying to use the on_crash hook to do that.
However the user feedback API requires an event-id to attach the user feedback to.

Background / Proposal

Our crashpad backend currently has no way to get the event-id of the to-be-sent event, as that is created on the server when the minidump is received.

According to @jan-auer, relay will use whatever id is provided in the special __sentry_event file which currently contains serialized scope information and is sent alongside crashpad minidumps.

It should be possible to generate a uuid ahead of time and serialize that into the __sentry_event file. When calling our hooks and provide a dummy event, we can then at least fill out the event id property so that customers can use it.

There might be the problem that the event/minidump needs to be sent before user feedback can be posted? Not entirely sure how the ordering and timing there could be guaranteed?

A possible flow could be this:

• App triggers crash hook, customer extracts event id from dummy event object.
• Customer spawns their own crash feedback gui using that event id.
• Crash handling is continued and crashpad captures the crash and sends a minidump using the event id embedded in the __sentry_event file.
• End user submits a feedback form about the crash using the event id.