expcapitaldev opened a new issue, #254: URL: https://github.com/apache/cordova-plugin-geolocation/issues/254
So, we know some additional information about bugs/specific/unexpected cases on android with approximate access, see https://github.com/apache/cordova-plugin-geolocation/pull/250. It is real good description for some cases. It is not relevant to api 30 because we can not get access to approximate level only, issue connected only for api 31>= because we will have two options for access level approximate and precise. And I did not find any unexpected cases on api level 33 too, but looks like need to check Webview version because it is connected to W3C and navigator.getCurrentPosition I tested on some devices login and found some cases: on android with api level 31 and 32 - google emulator chrome 91, api 31/32 approximate + getCurrentLocation + enableHighAccuracy false = timeout error - samsung chrome 104 api 31 approximate + getCurrentLocation + enableHighAccuracy false = result with additional popup about access to precise (for 31 api we ask two permissions, it is expected flow) but we can get coordinates without error - xiaomi 30 approximate/precise + getCurrentLocation + enableHighAccuracy false/true = timeout error - sm-g980F chrome 106 api 31 approximate + getCurrentLocation + enableHighAccuracy false = result without additional popup, but we ask 2 permissions, and we can get coordinates without error - SM-G781B chrome 106 api 31 approximate + getCurrentLocation + enableHighAccuracy false = result without additional popup, but we ask 2 permissions, and we can get coordinates without error - SM-G781B 106 api 31 approximate + getCurrentLocation + enableHighAccuracy false = result without additional popup, , but we ask 2 permissions and we can get coordinates without error Summary: Looks like bug why we can not get coordinates with enableHighAccuracy: false on api 31 and 32 connected for: - emulator only - google devices only - webview version from 91-106 and issue fixed in webview version 104+ I would appreciate any additional information on this matter. Goal: understanding the nuances and creating a universal flow, including the features of the work of different api versions As long as there is a plan, it is mandatory to get accurate access to geolocation for api 31 and 32, and only then can you already access "getCurrentPosition" and be sure that you should get the coordinates. Can not find any changelog for chromium(webview) on android -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
