Allow Geofence to trigger when app is killed #22
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @cladjules for the PR but I'm currently working on a solution using Thanks again! |
|
It would be great to have an ios part. Is it possible to have ios part merged? I have created a related issue already: #33 |
|
For iOS, According to this, I believe we need |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the geofence does not trigger the Javascript code while the app is killed, as there are no registers set yet.
In iOS, the app will automatically wake-up when the geofence is triggered and the listener will be registered after a few seconds.
In Android, I am instantiating the activity and launching the app, it's quite an ugly solution and I could use headless-js for that.
I haven't merged the latest release, but that gives an idea of how that could be achieved.