You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.40.1)
[!] Connected device
! No devices available
For there to be some way to tell if the Motion/Fitness API is enabled.
Actual Behavior
There is no way to tell if the Motion/Fitness API is enabled.
Context
This plugin's documentation stipulates a strong emphasis on the Motion/Fitness API to allow for battery-efficient location tracking. It would be great if there was a way we could get the status of this permission so that we can report to the user if is not enabled. I know that the plugin will request the permission the first time BackgroundGeolocation.start (or an equivalent) is called but that isn't enough to determine if the API is enabled or not.
Awesome plugin btw!
The text was updated successfully, but these errors were encountered:
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.
My Environment
flutter doctor
):Expected Behavior
For there to be some way to tell if the Motion/Fitness API is enabled.
Actual Behavior
There is no way to tell if the Motion/Fitness API is enabled.
Context
This plugin's documentation stipulates a strong emphasis on the Motion/Fitness API to allow for battery-efficient location tracking. It would be great if there was a way we could get the status of this permission so that we can report to the user if is not enabled. I know that the plugin will request the permission the first time
BackgroundGeolocation.start
(or an equivalent) is called but that isn't enough to determine if the API is enabled or not.Awesome plugin btw!
The text was updated successfully, but these errors were encountered: