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
It seems we do not always get the sentry crash reports for example every once in a while we have an issue where the app crashes on load, I believe this may be because we need to move it higher in the tree?
Right now Sentry depends on the Config entry file we have which means any issues that occur in that file may not be reported.
The text was updated successfully, but these errors were encountered:
I just experienced this on a project. I think it's because SENTRY_PROJECT_NAME and SENTRY_DSN are not part of the expo-main.yml GH action template. So when that action runs eas update, it pushes a new OTA update with a JS bundle that is missing those values. And so Sentry crashes the app on startup.
I verified this by sourcing all env variables on my local and then running the same eas update command found in expo-main.yml.
Aside, I would love to remove the mobile bootstrapper's hard dependency on Sentry and Rollbar. I think there's too much friction in bootstrapping a new mobile app.
It seems we do not always get the sentry crash reports for example every once in a while we have an issue where the app crashes on load, I believe this may be because we need to move it higher in the tree?
Right now Sentry depends on the Config entry file we have which means any issues that occur in that file may not be reported.
The text was updated successfully, but these errors were encountered: