You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Main process native crashes are reported on the next app start because they cause the app to exit. The only way we know that they've even occurred is that we find a minidump file on app start.
Maybe we could store the release somewhere and compare it to the current release before sending...
We already persist scope from the previous session so it wasn't complicated to also persist the release/environment too and override these before sending the event.
I've got a PR for this, I just need to work out what's causing some tests to start failing.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Electron SDK Version
4.1.2
Electron Version
19.1.9
What platform are you using?
MacOS
Link to Sentry event
No response
Steps to Reproduce
Expected Result
Actual Result
A crash event that happened on version X shows to happen on version X+1 and the sourcemaps for that couldn't be found.
The text was updated successfully, but these errors were encountered: