-
Notifications
You must be signed in to change notification settings - Fork 9
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Background Fetch Headless Class Not Found Exception #12
Comments
Ensure you’re using latest background-fetch |
I'm using version 1.20 of the plugin, and I'm still receiving the Class Not Found exception. Not sure if relevant, but our background geolocation config is below - in case there's some sort of conflict with this plugin?
|
|
I'm getting this same issue, even after installing the latest version and doing the above. It seems using Background Geolocation plugin and this plugin at the same time (since the former also uses background fetch?) causes issues? |
I'll come up with a workaround for this no problem |
@neil-119 They're designed to work together. Background Geolocation uses background-fetch internally for its own purposes. |
This issue appears on SDK version 19 for me. Any updates on solution?
|
@FranciZ I'm getting the same crash reports on google play for some phones (eg Android 4.3). Probably because of the targetApi(21) https://github.com/transistorsoft/transistor-background-fetch/blob/master/android/tsbackgroundfetch/src/main/java/com/transistorsoft/tsbackgroundfetch/FetchJobService.java#L12 For me the background service is not a mandatory feature, but a desired one. So I'll try disabling the feature on <21 sdk versions using Also might be useful looking it this answer: https://stackoverflow.com/a/58427864 |
When I try to enable headless mode on Android 8.1 / Nexus 6P, I get an error
java.lang.ClassNotFoundException
. We are running the latest version of NativeScript and the latest available version of your plugin. Not sure if relevant, but we're also using your background geolocation plugin.This is the log of the error:
Any ideas? A full re-build didn't help.
The text was updated successfully, but these errors were encountered: