Description
In the custom web apps, it's already possible to retrieve the user location through navigator.geolocation.getCurrentPosition().
This correctly prompts the user a "App wants to see your current location", and gets the coordinates as expected.
However, since it is a WebView requesting the location, you get a second prompt of "https://mywebsite.com wants access to your location".
Since we both maintain the content of the WebView and the native app itself, it makes sense to get rid of the duplicate prompt.
To make that work, we should integrate a new LocationProvider that acts the same.
Web app sends a "retrieve location" message to the provider -> Provider prompts user for location -> Retrieve location and send response
Preferably, options like exact: true/false would remain accessible for the Web to control.
This issue refers to both the Android and iOS libs, and should be integrated for both.
For more context or information, feel free to reach out 👍
Description
In the custom web apps, it's already possible to retrieve the user location through
navigator.geolocation.getCurrentPosition().This correctly prompts the user a "App wants to see your current location", and gets the coordinates as expected.
However, since it is a WebView requesting the location, you get a second prompt of "https://mywebsite.com wants access to your location".
Since we both maintain the content of the WebView and the native app itself, it makes sense to get rid of the duplicate prompt.
To make that work, we should integrate a new
LocationProviderthat acts the same.Web app sends a "retrieve location" message to the provider -> Provider prompts user for location -> Retrieve location and send response
Preferably, options like
exact: true/falsewould remain accessible for the Web to control.This issue refers to both the Android and iOS libs, and should be integrated for both.
For more context or information, feel free to reach out 👍