[X] Have you checked if similar request have already been reported?
Description
As of v0.3.3-beta, crashes are only saved to logs and embedded in the query string of the crash notification. Since the notification is the only user-facing report of the error, if anything happens to that notification (accidentally dismissed, hidden by DnD, or corrupted by a failure to base64 encode) the user is left in the dark.
A potential solution would be to persist just the unhandled exception to disk, which can then be loaded on startup perhaps with a prompt to report the error to GitHub.
Before you start...
Description
As of v0.3.3-beta, crashes are only saved to logs and embedded in the query string of the crash notification. Since the notification is the only user-facing report of the error, if anything happens to that notification (accidentally dismissed, hidden by DnD, or corrupted by a failure to base64 encode) the user is left in the dark.
A potential solution would be to persist just the unhandled exception to disk, which can then be loaded on startup perhaps with a prompt to report the error to GitHub.
Alternative solutions
No response
Relevant Assets
No response