We already write the crash timestamp to the crash-marker in sentry__write_crash_marker. Since we now have an event_id for all backends (since #1319), we could additionally write this to the same file & provide a method to fetch this value.
Depending on how this value is to be used, we could additionally continue with #885 (comment) and the sentry_options_set_on_crashed_last_run() proposal, allowing users to add data to an envelope. This is probably out-of-scope for the event_id issue, and we might split this issue up in two.
We already write the crash timestamp to the crash-marker in
sentry__write_crash_marker. Since we now have anevent_idfor all backends (since #1319), we could additionally write this to the same file & provide a method to fetch this value.Depending on how this value is to be used, we could additionally continue with #885 (comment) and the
sentry_options_set_on_crashed_last_run()proposal, allowing users to add data to an envelope. This is probably out-of-scope for theevent_idissue, and we might split this issue up in two.