-
Notifications
You must be signed in to change notification settings - Fork 198
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
Unexpected request for background location #173
Comments
@Birowsky Do you have any other plugins in your app that could use the location permission? Please run Your app would only request background location if |
Yes, cordova-background-geolocation. That's the plugin that adds the background location capability. But to test, I removed the plugin and added the capability by hand, with OneSignal being the only suspicious plugin installed. That's when I noticed the popup. Since then, the project got restructured, and we moved to firebase for notifications. So I can assist you only by memory. |
Is there any update on this? We're facing the same issue. We are using |
I have updated the SDK with a If anyone is still encountering this issue please feel free to reply (with a list of your plugins) and I'll be happy to investigate. |
We were trying to use Onesignal with our app, which also uses I tried adding the
This seems to only happen when i'm upgrading/overwriting the app with a Testflight version. If I install the app fresh from Testflight I only get a location permission dialog once, as it should be. We wouldn't mind using the location feature, but having the app ask for permission again when users have already given it, is a non-starter for us. So unless there is a fix or solution, we can't use OneSignal. |
When certain conditions are met, the SDK requests background location, which opens permissions prompt:
To reproduce:
What i've noticed is that if the app doesn't have background location as a capability, this wouldn't happen.
Here's demo: https://youtu.be/qEUpoFQeELs
And then i noticed this issue, which points out that OneSignal SDK does do some unexpected stuff in the background.
Is there a way to disable all location stuff for OneSignal? At least as an intermediate solution for the time being?
The text was updated successfully, but these errors were encountered: