-
Notifications
You must be signed in to change notification settings - Fork 277
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
How Can I Know If GPS is Enabled and If not How Can I open settings from APP #350
Comments
Listen to providerchange event. |
@christocracy , Any API equivalent to: |
No, but I believe there are 3rd-party plugins that can do this. |
providerChange event listener is not working in my case.. I've written it like:
Still when I turn off GPS or If I turn it on again.. Nothing is getting printed in logs and no Alert is coming. Also There is one more issue, Can you please help in this? |
You're not attempting to boot this in the browser, are you? |
What is the error returned from |
|
It says invalid action.
…On May 23, 2017 8:33 PM, "Chris Scott" ***@***.***> wrote:
What is the error returned from failureCallbackFn?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#350 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYzDUsLtOeDY9muFePcIrgcCbJ25oys2ks5r8vUigaJpZM4NjTv4>
.
|
Show me your |
Though `configure` is falling, call to `start` is working fine and it is
fetching correctly fetching locations.
|
Show me your |
@christocracy,
|
@christocracy |
You problem is this:
You need to remove that. You can't use both Mauron85's old fork in addition to this plugin. This plugin has a different API and config params. You need to start from scratch implementing my plugin. Your Javascript code for Mauron85's version is incompatible with mine. |
My plugin includes my iOS background-fetch plugin as a dependency:
This plugin will fire its fetch event typically every 15min, even while the device is stationary. |
Can I make it customizable, Say If I want location after every 2 mins (ios)? Can I do it? Thanks for your help :). |
iOS background-fetch API's minimum interval is 15 min. |
Hi, I uninstalled another plugin and tested this one. Now Just one question; Every time I call I don't want to show location sharing permission dialog box if permission is already given. Any idea How can we do it? Really Appreciate your help. |
The plugin does not ask for location permission if already granted. |
The question for you is: "why is the location permission being revoked causing the plugin to have to re-ask for permission?" |
I was uninstalling and re-installing app for testing purpose and thats why it was asking for location permissions again and again. Now That issue is resolved. As I mentioned earlier
As Location update interval is 15mins on IOS; I tried to use It works fine in both IOS and Android in foreground and background mode; But There is one issue which I noticed recently; After some time Let us say 10mins; instead of firing Is it because of my config settings?
Or is it something else? Thanks in advance. and as mentioned in documentation; And what is the minimum distance needs to be travelled to trigger |
You are getting way off topic from the original subject "How Can I Know If GPS is Enabled and If not How Can I open settings from APP". This issue is closed. I will talk no further on this thread. |
@christocracy, Created a new Thread: #354 |
I want to know if GPS is enabled and app is able to access the GPS, If any of this is not true, Then I'll like to open settings. Is this possible?
Environment
Plugin version: 2.7.0
Platform: Android
OS version: 6
Cordova version (
cordova -v
): 6.5.0Plugin config
Expected Behavior
I want to check GPS/location settings before start (if location is not enabled, We can show some alert or open settings)
Actual Behavior
It just asks that APP requires Permission to access Location.
Context
I want to check GPS/location settings before start (if location is not enabled, I want to open settings) Is it possible?
The text was updated successfully, but these errors were encountered: