Geolocation working on android 13,14 even 8 but not on android 12 function does not call no error in console

[adeel399]

Geolocation working on android 13,14 even 8 but not on android 12 function does not call no error in console

[adeel399]

i Forget to mention even in android 12 it asked for location permission every thing seems to be fine regarding permission

[breautek]

Are you requesting FINE or COARSE location? (e.g. do you have high accuracy enabled or disabled?)

Android 12 has a known issue where requesting coarse location doesn't work as expected and instead location requests will timeout.

[adeel399]

const coordinates = await capacitorgeolocation.getCurrentPosition({
enableHighAccuracy: false,
});
right now my code
before i did not added any option (not working in 12)
then i added that option still not working

[adeel399]

My androidmanifest

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-feature android:name="android.hardware.location.gps" />
<uses-permission android:name="android.permission.INTERNET" />

[breautek]

const coordinates = await capacitorgeolocation.getCurrentPosition({ enableHighAccuracy: false, }); right now my code before i did not added any option (not working in 12) then i added that option still not working

Sounds like you're hitting the android bug that I linked earlier. I think the only known workaround is to request high accuracy location (which translates to FINE location natively).

e.g.

const coordinates = await capacitorgeolocation.getCurrentPosition({
enableHighAccuracy: true,
});

When enableHighAccuracy is disabled, then COARSE location is used and location requests is suppose to report on location updates within 1,000km or so. The bug describes a situation where this doesn't work on Android 12. Having enableHighAccuracy enabled makes the underlying API to use FINE location instead which does work as intended on Android 12.

If you don't actually need FINE location, then perhaps it might be worth only enabling it on Android 12 devices.

This comment suggest that the issue is believed to be fixed but it will require an Android OS update and whether that update is available may be subjected to your carrier.

[adeel399]

So you suggesting enableHighAccuracy:true will resolve the issue on android 12?

[adeel399]

enableHighAccuracy:true
this does not fix the issue

[breautek]

enableHighAccuracy:true this does not fix the issue

Can you confirm your device location settings?

Settings -> Location -> Location Services

Google Location Accuracy should be enabled, otherwise high accuracy / FINE location will not work.

Additionally, the app permission should have Precise enabled:

Settings -> Location -> App location permissions -> Your Application

Ensure location access is enabled with precise location.

If either precise location or Google Location Accuracy is disabled, then regardless of the app requesting high accuracy the device will only return COARSE location which will be a victim of the aforementioned android 12 bug.

The app permissions will be set by the user on the first time they use your app, but it's possible they disallow precise permission on the permission prompt which will trigger the android 12 bug. Google Location Accuracy is a user setting that can't be programmatically controlled, the user must enable it to enable high accuracy location. Usually it's enabled by default from factory.

[adeel399]

ok i ll update you regarding that tommorow