Skip to content
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

IOS it doesn't work when app is killed(Android is working) #309

Open
FetFrumos opened this issue Feb 3, 2022 · 4 comments
Open

IOS it doesn't work when app is killed(Android is working) #309

FetFrumos opened this issue Feb 3, 2022 · 4 comments

Comments

@FetFrumos
Copy link

I using last version plugin background_locator: ^1.6.12. But example doesn't work in IOS when app is killed. it works in android perfectly.
I followed all the instructions in the wiki. What could be the reason? Any advice - I'll be grateful. By the way, the example can be updated.

@FetFrumos
Copy link
Author

any news? anybody here?

@treacks5
Copy link

treacks5 commented Feb 18, 2022

Same here.
Potentially same issue #291 🤷‍♂️

Details :

I have a flutter iOS mobile app that display a push notification (using 'https://fcm.googleapis.com/fcm/send') every time the location callback is trigger.

I receive the location notification on foreground and background, but not when I manually kill the app.
What is curious is that I can see the native navigation icon on the top left (next to the iPhone time) even when the app is killed. So I suppose that the background_locator location service is working great but it is just that the callback is not triggered.

background_locator version is 1.6.12

@Mayb3Nots
Copy link

When you terminate the app did you test after moving the location about 500m away? Because the way IOS works is it will only send the device's location after ~500m location change when the app is terminated. If it doesn't move it won't trigger.

@FetFrumos
Copy link
Author

yes, after the application is killed - it does not work, on any melt. @Mayb3Nots do you have a working example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants