-
Notifications
You must be signed in to change notification settings - Fork 231
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
onLocation is firing from older instances #231
Comments
There is no "multiple instances" of
This makes no sense. What makes you think the locations are "older"? |
The plugin is like an electronic device with a power button.
|
Have you read the API docs for onLocation |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You may also mark this issue as a "discussion" and I will leave this open. |
Closing this issue after a prolonged period of inactivity. Fell free to reopen this issue, if this still affecting you. |
Your Environment
flutter doctor
):[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.4 19E287, locale pt-BR)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
[✓] Android Studio (version 3.6)
[✓] VS Code (version 1.44.0)
[✓] Connected device (1 available)
• No issues found!
Expected Behavior
When the .stop is invoked, then all the further locations must be destroyed
Actual Behavior
When I stop an instance, and then I start a new one, onLocation event is fired with locations from the older instance.
Steps to Reproduce
Context
I'm trying to start/stop the service and capturing the locations from these user`s manual actions
The text was updated successfully, but these errors were encountered: