Find an associated Android crash report: If your Android app is on Google Play, refer to the crashes section of the Google Play Console, or connect your Android device to your computer and run adb logcat to view the streaming logs.If not, refer to their "Diagnosing Issues Using Crash Reports and Device Logs" guide. Find an associated iOS crash report: If your iOS app is on TestFlight or the App Store, you can use the Crashes Organizer in Xcode.Find an associated JavaScript crash report: Check your JavaScript error reporting service (such as Sentry).Reproduce the crash (either using your production app, or the Expo Go app).
It's important now to reproduce the issue, and, even if you can't do that, to find any related crash reports. This can be a really frustrating scenario, since it gives you very little information to go off of on first glance. Using console.log for debugging isn't considered the best practice, but it's fast, easy, and oftentimes provides some illuminating information