New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android Dev Client Unstable when using Background Tasks: ClassNotFoundException: host.exp.exponent.taskManager.ExpoHeadlessAppLoader #9415
Comments
Looking into more debugging, it looks like this only appears when using background tasks with |
I can confirm this, I'm not using the
|
They say this issue is fixed in SDK 39 but I haven't seen anyone verify it. Can someone from Expo comment on this issue...it's pretty severe. Made a forum posting trying to get some clarity on where this is at: https://forums.expo.io/t/startlocationupdatesasync-crashes-app-on-sdk-38-android-managed/42035 |
I have upgraded expo to 39, and this issue still causes problems, few problems. First is like @mbretter said, when you kill process expo, or even .apk fails, and there is no way you can start them again, unless you clear storage, second one is that when I start app first time, after install .apk, locations are not working, then when i logout, and login again it start working. Can someone from expo tell us something more about this? |
I'm too on expo 39 and have this error, and not still resolved |
I am getting this one |
hello! the specific issue mentioned in the OP ( if you encounter other related issues after updating to the latest version then please let us know in a new issue with all of the relevant error information that we request. |
馃悰 Bug Report
Summary of Issue
The Android Expo client gets unstable when using background tasks. From the first time a client app with background tasks is started inside the client, the client gets unstable and crashes on start (even before getting to the app selector screen). Aparrently, sometimes it can get to the app selector and selection of an app is possible. After that, the app runs stable until the next restart.
The adb log on a crash looks this:
As the app can be started after multiple tries and runs stable after that, I assume this is some kind of race condition. Note: the crash appears before getting to the app selector screen, so I guess it is not an issue with the client app(s).
Also, the issue does not appear in a built standalone app, only in the Expo client. The client is nearly unusable due to this issue.
Environment - output of
expo diagnostics
& the platform(s) you're targetingAndroid device is a OnePlus 6, Android 10, Expo client version 2.16.1.
Reproducible Demo
Steps to Reproduce
Create an app with a background task. The background task pulls in Location info. Run it in the Android client.
Expected Behavior vs Actual Behavior
Expected: run the app without issue and stable on reloads. Actual: Expo client is crashing on startup, crashing on client app startup, crashing at app reload. It is crashing all over the place.
The text was updated successfully, but these errors were encountered: