WAI
Status Update
No update yet.
Comments
st...@simplymadeapps.com
I would also like to add - similar issues are also happening on other API versions too. If you follow the StackOverflow question that I posted, users are having troubles registering Geofences in general. I am randomly having troubles on my Android 8.0 and Android 9.0 devices. It seems to randomly just not work and throw the CommonStatusCodes ERROR #13 which is "no extra details provided". This issue may be more widespread than the Android Q Beta. However, from my testing, the Android Q Beta version was always consistent. If I had the permission set to "Allow only while using the app" I would always get the error and if I set the permission to "Allow all the time" it would always work successfully. I am not sure how to resolve the problem on the other API versions because they do not have the new location permission. Hopefully that helps.
ve...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
lu...@csmotion.com.au
Hi guys,
To expand on this for the stack overflow post-
I've uploaded a basic example project which demonstrates this issue here. This simply happens when adding geofences, doesn't matter if this is done through GeofencingClient or a LocationServices.GeofencingApi instance.
https://drive.google.com/file/d/1VgezU7385hAx091XA52aOp8Y8sJzQgKf/view?usp=sharing
This issue happens 90-100% of the time on PlayServices version 17.x, and does not seem to occur on PlayServices 16.x.
This is happening on various devices from Lollipop all the way to Pie, and is affecting builds previously working with no code changes or deployments. This has only recently started happening. If you run the example project, which simply removes and adds geofences, it will very quickly get into a state where adding the geofences return ApiException status 13 and no longer works.
To expand on this for the stack overflow post-
I've uploaded a basic example project which demonstrates this issue here. This simply happens when adding geofences, doesn't matter if this is done through GeofencingClient or a LocationServices.GeofencingApi instance.
This issue happens 90-100% of the time on PlayServices version 17.x, and does not seem to occur on PlayServices 16.x.
This is happening on various devices from Lollipop all the way to Pie, and is affecting builds previously working with no code changes or deployments. This has only recently started happening. If you run the example project, which simply removes and adds geofences, it will very quickly get into a state where adding the geofences return ApiException status 13 and no longer works.
[Deleted User] <[Deleted User]>
Hi guys,
what is the solution for this issue?
what is the solution for this issue?
ra...@gmail.com
Hi Guys, Please can we get an ETA for this fix as it's impacting my app users on the Google Play store?
I have shared my device log which shows the APIException status 13 here
https://drive.google.com/open?id=1FYMUQNZ2VeB87d0XZqTgIEBLjiY6VrXj
So far i have found that it happens on various devices with Android 9.
I am getting increasing complaints from irate Android phone users for an issue that I cannot fix in the app. This was working absolutely fine until a Google update broke it.
This is my apphttps://play.google.com/store/apps/details?id=com.intsoftdev.nationalrail&hl=en_GB
As previous users have mentioned the issue is random and has started happening recently since an update.
Let me know if you need more info.
I have shared my device log which shows the APIException status 13 here
So far i have found that it happens on various devices with Android 9.
I am getting increasing complaints from irate Android phone users for an issue that I cannot fix in the app. This was working absolutely fine until a Google update broke it.
This is my app
As previous users have mentioned the issue is random and has started happening recently since an update.
Let me know if you need more info.
ve...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
pa...@nianticlabs.com
I am running Android 8 on my device, Google Play Services version 16.0.0 and I just noticed this happening 100% of the time to me today.
I'm simply calling:
val task = geofencingClient.addGeofences(request, pendingIntent)
val result = task.await()
and getting:
Caused by: java.util.concurrent.ExecutionException: com.google.android.gms.common.api.ApiException: 13:
com.google.android.gms.tasks.Tasks.zzb(Unknown Source:61)
com.google.android.gms.tasks.Tasks.await(Unknown Source:23)
I'm simply calling:
val task = geofencingClient.addGeofences(request, pendingIntent)
val result = task.await()
and getting:
Caused by: java.util.concurrent.ExecutionException: com.google.android.gms.common.api.ApiException: 13:
com.google.android.gms.tasks.Tasks.zzb(Unknown Source:61)
com.google.android.gms.tasks.Tasks.await(Unknown Source:23)
pa...@nianticlabs.com
Sorry, Android 9 on my device.
pa...@nianticlabs.com
Update:
I have 2 Pixel 2s Both are running Android 9 build Pq3A.190605.003
One one phone adding geofences works consistently. On the other one if fails consistently.
I have 2 Pixel 2s Both are running Android 9 build Pq3A.190605.003
One one phone adding geofences works consistently. On the other one if fails consistently.
lu...@csmotion.com.au
To everyone following the thread, I don't think this is restricted to an OS version, this is affecting every device in my drawer from KitKat to Pie. It seems like it is from one of the later PlayServices versions deployed around the 11th. I've found consistently the 17.x versions are causing the issue. Any devices that have not updated and are still on a 16.x version are unaffected, and once they've updated to 17.x the issue starts happening on them
st...@simplymadeapps.com
I agree with #11, I also experience this on multiple different versions of the OS.
For the Google employees - it may be helpful to move this issue to another section or assign it to a different team as this doesn't apply solely to the Android Q Beta. It likely is a problem more with Google Play Services than Android Q Beta.
I am guessing that it has at least something to do with the new Android Q changes because I see the exact same error 100% of the time when I am running Android Q with the "Allow only while using the app" location permission. The latest version of Google Play Services was released right around the same time as the Android Q Beta. Something weird is going on and it is almost like Google Play Services is checking for the new "Allow only while using the app" permission on devices that aren't on Android Q yet. It feels like in the latest Google Play Services version they added some additional check that is causing these problems - and it is also right around the time as the Android Q Beta. Maybe some of the changes they added in Google Play Services for Android Q Beta devices are causing the problem. That is obviously just pure speculation at this point but it will hopefully be helpful to any Google employees that are working on this issue.
For the Google employees - it may be helpful to move this issue to another section or assign it to a different team as this doesn't apply solely to the Android Q Beta. It likely is a problem more with Google Play Services than Android Q Beta.
I am guessing that it has at least something to do with the new Android Q changes because I see the exact same error 100% of the time when I am running Android Q with the "Allow only while using the app" location permission. The latest version of Google Play Services was released right around the same time as the Android Q Beta. Something weird is going on and it is almost like Google Play Services is checking for the new "Allow only while using the app" permission on devices that aren't on Android Q yet. It feels like in the latest Google Play Services version they added some additional check that is causing these problems - and it is also right around the time as the Android Q Beta. Maybe some of the changes they added in Google Play Services for Android Q Beta devices are causing the problem. That is obviously just pure speculation at this point but it will hopefully be helpful to any Google employees that are working on this issue.
pa...@nianticlabs.com
We spoke with Google play team today and they say that the issue is fixed. I was able to verify that it's working for me now on the device that was previously failing. Would be interested if others see the same thing.
No software update was needed on my phone. This makes me wonder what was wrong in the first place - seems like my device shouldn't depend on some random Google server out there somewhere.
At least it's fixed.
No software update was needed on my phone. This makes me wonder what was wrong in the first place - seems like my device shouldn't depend on some random Google server out there somewhere.
At least it's fixed.
lu...@csmotion.com.au
Can confirm it's also mysteriously working again on my end with devices that previously didn't without any code changes
ve...@google.com
We have looked into the issue you have reported and would like to inform that this is working as intended. Please find the below details:
By design, apps need background location permission to use Geofencing API. Foreground only permission will prevent Geofencing from working.
By design, apps need background location permission to use Geofencing API. Foreground only permission will prevent Geofencing from working.
Description
* Which Android Beta build are you using? See Settings > About phone > Build number (for example PPP5.180610.010).
QPP4.190502.019
* 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.)
Set your Location permission to "Allow only while using the app" and try to start monitoring a Geofence according to the Geofencing documentation. The OnFailureListener will trigger an error code #13 and the Geofence registration will fail. Setting the Location permission to "Allow all the time" and try again and the Geofence will be added successfully.
This may be an issue with the latest Google Play Services version. There is a new StackOverflow question with a decent following here...
* Issue Category
Runtime Permissions
Google Play Services
Geofences
Location Permissions
* What was the expected result?
I would've expected the Geofence to get added by the system but it just wouldn't trigger unless the application was in the foreground or while in use.
* Can you provide the API document where this expected behavior is explained?
In this document (
* What was the actual result?
Unable to register any Geofences with the new "Allow only while using the app" permission
Is this expected behavior? Should we prevent the user from registering Geofences unless the permission is set to "Allow all the time"? What happens if we have registered a Geofence and a user later changes their permission to "Allow only while using the app"? Would the Geofence be unregistered or would it still be registered and only work when the app is in the foreground?
Thanks!