Obsolete
Status Update
No update yet.
Comments
ve...@google.com
ve...@google.com
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ar...@google.com
We've deferred this issue for consideration in a future release. Thank you for your time to make Android better. In case you want to provide more information with respect to this bug, please file a bug in AOSP via "https://goo.gl/TbMiIO
ad...@google.com
sa...@google.com
Thank you for your feedback. We will be closing the issue as “won't fix - obsolete”. If this issue is still reproducible, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.
Description
QPP4.190502.019
* Is this a regression from P to Q?
No
* What device are you using? (for example, Pixel XL)
Pixel
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
1. Start app using geofence and targeting API level 27
2. On location permission requiest, choose "Allow only while using the app"
3. Create geofence failed
* Issue Category e.g. Famework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Runtime Permission.
* What was the expected result?
At first, user cannot see the option "Allow only while using the app".
In additon, the background permission should be granted automatically.
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
I saw "while using the app" option. and geofence creation failed.
`adb shell pm dump` showed following result:
```
runtime permissions:
android.permission.ACCESS_FINE_LOCATION: granted=true, flags=[ USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
android.permission.ACCESS_COARSE_LOCATION: granted=true, flags=[ REVOKE_WHEN_REQUESTED|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
android.permission.ACCESS_BACKGROUND_LOCATION: granted=false, flags=[ USER_SET|REVOKE_WHEN_REQUESTED|USER_SENSITIVE_WHEN_GRANTED|USER_SENSITIVE_WHEN_DENIED]
disabledComponents:
```
* Relevant logcat output.
```
07-05 21:20:09.492 10044 10044 V GrantPermissionsActivity: Permission grant result requestId=-5095224186265222891 callingUid=10275 callingPackage=com.example.dagezi.geofencetest permission=android.permission.ACCESS_FINE_LOCATION isImplicit=false result=4
07-05 21:20:09.492 10044 10044 V GrantPermissionsActivity: Permission grant result requestId=-5095224186265222891 callingUid=10275 callingPackage=com.example.dagezi.geofencetest permission=android.permission.ACCESS_COARSE_LOCATION isImplicit=true result=4
07-05 21:20:09.494 10044 10044 V GrantPermissionsActivity: Permission grant result requestId=-5095224186265222891 callingUid=10275 callingPackage=com.example.dagezi.geofencetest permission=android.permission.ACCESS_BACKGROUND_LOCATION isImplicit=true result=6
07-05 21:20:09.510 11116 11116 D DGZ : Permission granted
07-05 21:20:12.878 2159 3342 W GLMSImpl: com.example.dagezi.geofencetest doesn't have sufficient location permission to request geofence.
```
* Link to captured Android bug report (shared privately in Drive.)
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)