Added requestStateForRegion after didStartMonitoringForRegion on iOS #125
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
|
+1 on this PR. Any comments on if it will be accepted? |
|
Really wanted something like this. Any updates? |
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.
I believe this was discussed before but never implemented :
This allows to check wether the user is inside/outside of a geofence when adding/updating it on iOS.
I am not working with Android for now so I am not sure that is the state of things although it seems to be that I previously read that this plugin does do this for Android ?
BTW, this makes use of a delay function as calling manager.requestStateForRegion straight after starting to monitor a region seems to sometimes result in not determined states.
Or perhaps this could be configured as an option when adding/updating a geofence ?