

› Press ? │ show all - there isn't anything particularly useful in those adb logs. Users/michaelgates/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am start -a -d exp://10.2.190.2:19000

Users/michaelgates/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell monkey -p -c 1 Users/michaelgates/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell dumpsys package Users/michaelgates/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell pm list packages Users/michaelgates/Library/Android/sdk/platform-tools/adb -s emulator-5554 reverse tcp:19000 tcp:19000 Users/michaelgates/Library/Android/sdk/platform-tools/adb -s emulator-5554 emu avd name Users/michaelgates/Library/Android/sdk/platform-tools/adb devices -l Running expo with debug logging yields nothing out of the ordinary. I looked through and see a few warnings/errors but googling around didn't seem to lead me to any solutions. Here is all I can see in the ADB logs when the crash happens. Machine info: macOS Monterey 12.4 on the 16" MacBook Pro M1 Max.

I tried reproducing with this project and the issue persists, so it's not just my own. And on the very slight chance the expo go app doesn't crash and the app doesn't crash, it might work or it may be frozen or it may crash after just a few seconds. the 1% of the time it doesn't crash, the app will load and then crash. However, upon the Expo Go client opening on the Android emulator, it crashes almost immediately approximately 99% of the time. I can start the expo server just fine, and I am able to send the app to Android.
