Unfortunately, Expo has stopped


#1

My app loads and functions on iOS, but on Android the expo app is crashing. On Android I can load the landing, login, signup screens, but when firing login function the expo app quits and gives error “Unfortunately, Expo has stopped”. However the sign-up function is working properly.


#2

What errors do you see in the device log?


#3

It would not send any errors to the log, it would only crash. I’ve solved some of the issue, and it had to do with react native router flux and the tabs with that


#4

Okay great. Glad you’ve been able to narrow it down!


#5

Same problem with Expo using Genymotion, on MacOS, using React Navigation …


#6

I’m seeing the same issue with Expo 23.0.4, react-native 0.50.3, react-navigation on the regular android simulator and a physical Android device both running 8.0 (Oreo)


#7

Anyone got any solution ? I am getting the same issue.
I got this in my cli console

..............
:app:installDevDebug
Installing APK 'app-dev-debug.apk' on 'SM-G610F - 7.0' for app:devDebug
Installed on 1 device.

BUILD SUCCESSFUL

Total time: 3 mins 37.821 secs
Starting: Intent { cmp=host.exp.exponent/.LauncherActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mBaseDisplayId=0 mFlags=0 } }

But when I try to run the app in my device I got the popup “Sample Expo App has stopped … Close app”
Then it got closed.


#8

Hi, first of all I know that this kind of errors are very annoying… And no errors from expo or debugger whatsoever.
I had the same issue, turned out a syntax error in render function was causing the crash. It might be an extra curly brace or similar.

Cheers…


#9

I have the same issue…I am using Expo on the web…app runs on IOS and doesn’t on android.On android it shows the error “Expo has stopped.open the app again”.


#10

Unfortunately i’m having the same issue. It happens on Android(iOS is fine) when navigating through the app, we’re using:
“expo”: “^30.0.0”,
“react-native”: “github:expo/react-native#sdk-30.0.0”,
“react-navigation”: “^1.5.12”,

Is there any way to debug this other than detaching?


#11

Hi @scotttharvey, I have the same issue and am also using react-native-router-flux. Do you happen to remember how you fixed it? Thanks.