fix: when using playServices provider the getCurrentPosition error callback is never called #302
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.
When using playServices provider the getCurrentPosition error callback is never called
Overview
In Android platform, when you are using the playServices as location provider and any error occurs in checkLocationSettings phase, it always emits the geolocationError event, which is only listenned by the watchPosition feature. So, when you are using the getCurrentPosition feature, the error callback is never being called.
Test Plan
Using the example project in this repository, do the following: