During an app that is in
standalone mode, I may get an error or two, and the way that Expo/RN seems to handle it is by showing the splash screen indefinitely. This doesn’t seem to be happening at a point when I’m capturing a Sentry error, which makes the entire process frustrating, because it seems that I need to know what the error is so that I can capture it … but if someone knew that, then they’d just go ahead and fix the error.
Steps to reproduce:
- Have an app deployed live
- Run into some error
By doing steps 1 and 2, at least on an Android device with SDK 39, when an error occurs, the splash screen will come up and it will stay there. What do people typically do to address errors to prevent this from happening? I’d rather the app crash so that at least the user knows something bad happened.
SDK version: 39
Platforms: Android (so far, I’ve yet to test iOS)