Since I upgrade to the SDK 39, various things are broken in my app (fonts not loading, Async storage items not getting fetch…). It might all be caused by one common issue, but the biggest issue is that I cannot debug my app anymore to track it down.
When I activate remote js debugging, the app won’t start. It crashes during the splash screen loading.
I have same problem on version 38, just Expo has stopped, and there is no way yo can start it again. I think it is related to task_manager which i Use for background location functionality.
Same issue here, updating SDK 38 → 39.
I had to stash the change and disable remote debugger and start again to resolve this issue.
iOS works fine but fails with Android.
try {
await SplashScreen.preventAutoHideAsync();
// Load my fonts, async storage data, etc. here
// Never get done because of the error on SplashScreen above
} catch (e) {
console.warn(e);
await SplashScreen.hideAsync();
}
It is not related to the crash when debugging, but it did come with sdk 39, so I thought I might let others know if they use the same loading logic
A temporary solution for those who are stuck in crash loop
Go to ‘app info’ of Expo app and clear App data. It will log you out, delete history and other app data but will also disable Debug Remote JS and you will be able to use expo client again (without debugging, of course).