-
Notifications
You must be signed in to change notification settings - Fork 52
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
[BUG] Doesn't work in real devices #57
Comments
enableBackgroundExecution requires the initialization to be finished. In the emulator, the initialization is presumably fast enough to be finished by chance. You should probably use await:
If you need to do it in a non-async function, you can also do the following:
|
Same issue for me.
|
The problem was in my real device configuration! I allowed my app to use location all the time, and it started working in the background too! |
There's definitely an issue on real devices. You have to initialise the configuration twice in order for it to work. |
same happened to me, on emulator works but on real devices throws java.lang.RuntimeException: Unable to start service de.julianassmann.flutter_background.IsolateHolderService@8ca558 with Intent { act=START cmp=com.imvaswms.invaswmsdm/de.julianassmann.flutter_background.IsolateHolderService }: java.lang.IllegalArgumentException |
Unable to start service Intent { act=START cmp=com.deskbtm.nitmgpt/de.julianassmann.flutter_background.IsolateHolderService } U=0: not found |
Describe the bug
It works in emulator but not in a real device
To Reproduce
Expected behavior
I am calling both initialize and enablebackgroundexecution at the same time. It works on emulator but not in a real device
Smartphone:
Logs:
No Exception/Error Found.
The text was updated successfully, but these errors were encountered: