[TIMOB-28121] Android: Add Ti.Geolocation.requestTemporaryFullAccuracyAuthorization() support
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Low |
Status | Open |
Resolution | Unresolved |
Affected Version/s | Release 9.2.0 |
Fix Version/s | n/a |
Components | Android |
Labels | android, geolocation, parity, permission |
Reporter | Joshua Quick |
Assignee | Joshua Quick |
Created | 2020-09-10T05:57:59.000+0000 |
Updated | 2021-02-22T18:36:56.000+0000 |
Description
*Summary:*
As of Titanium 9.2.0, we added the [requestTemporaryFullAccuracyAuthorization()](https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Geolocation-method-requestTemporaryFullAccuracyAuthorization) method for iOS 14 which was intended to request the end-user for permission to use the GPS in case access has expired or was disabled. We should add this method to Android for parity to make it easier to write cross-platform code.
*To-Do:*
On Android, the [Ti.Geolocation.requestTemporaryFullAccuracyAuthorization()](https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Geolocation-method-requestTemporaryFullAccuracyAuthorization) method should just call the native [Ti.Geolocation.requestLocationPermissions()](https://docs.appcelerator.com/platform/latest/#!/api/Titanium.Geolocation-method-requestLocationPermissions) method, which requests the end-user for the
"android.permission.ACCESS_FINE_LOCATION"
permission. This is the closest equivalent on Android.
*Note:*
On Android, the "android.permission.ACCESS_FINE_LOCATION"
and "android.permission.ACCESS_COARSE_LOCATION"
permissions are always granted together. The end-user is unable to deny the FINE permission and keep the COARSE permission afterwards. They can only be both denied together afterwards. So, this isn't something we have to worry about on this platform.
No comments