Fixed
Status Update
No update yet.
Comments
gr...@tablet.academy
This is a hard one. We can't easily read native crashes from that Motorola device since their system image is not public. I assume you can't reproduce this either, but if possible can you try using WorkManager 2.0.0 or 1.0.1-rc01? This would help track down the possible changes that might have introduced this issue. Thanks!
le...@google.com
We actually did reproduce it, the current store version of Pocket Casts has WorkManager 2.0.0 and this bug if you want to try and test something. I will try 1.0.1-rc01 and report back.
gr...@tablet.academy
Is there a difference between 1.0.1 and 2.0.1? We tried 2.0.1 and it was crashing, if there is a difference I can try 1.0.1 but I thought they were the same?
gr...@tablet.academy
Can you also describe how you trigger the bug and which devices manifest the problem? Is it just running the app? Is it doing something specific?
le...@google.com
We are testing on a Moto X running Android 6.0 but our play store report shows numerous motorola devices are crashing as the attached screenshots show. We just downloaded a bunch of episodes (which uses workmanager) and eventually it started crashing, it would then crash at start up every time.
gr...@tablet.academy
So to answer your earlier question, 1.0.1 should be equivalent but I think there may be some small differences in Room between 1.0 and 2.0 and since this crash seems related to Room, that's why we were asking if you could check to see if you can reproduce it on 1.x.
Regarding the initial crash, do you have any logs for that?
Regarding the initial crash, do you have any logs for that?
le...@google.com
This is the log I have. Hope it helps. Will test 1.0.1 for you
gr...@tablet.academy
The logs are too short its just the crash and not much else before. :(
If the phone happens to be rooted and you are OK with sharing DB queries then you can enable SQL logging so we can see the queries that are occurring:
adb shell setprop log.tag.SQLiteStatements VERBOSE
adb shell stop
adb shell start
It would also be great if you can send us a bigger set of logs, or even better yet a bugreport after the crash occurs. (https://developer.android.com/studio/debug/bug-report )
If the phone happens to be rooted and you are OK with sharing DB queries then you can enable SQL logging so we can see the queries that are occurring:
adb shell setprop log.tag.SQLiteStatements VERBOSE
adb shell stop
adb shell start
It would also be great if you can send us a bigger set of logs, or even better yet a bugreport after the crash occurs. (
le...@google.com
We can't root the phone sorry, we might be able to send a bug report though
gr...@tablet.academy
We have a bug report from the crash already actually
jo...@kamiapp.com
We haven't been able to get the crash to happen on 1.0.1 so far
le...@google.com
va...@google.com
With a version of WorkManager that you are able to reproduce the issue, can you try adding Room 2.1.0-alpha06 as a dependency, effectively upgrading WorkManager's runtime dependency of Room?
Can you also enable WorkManager logs using setMinimumLoggingLevel(Log.DEBUG)https://developer.android.com/topic/libraries/architecture/workmanager/advanced/custom-configuration
If you observe the crash please do take a bug report. If possible also dump dbinfo for the app's package: adb shell dumpsys dbinfo <package-name>
Can you also enable WorkManager logs using setMinimumLoggingLevel(Log.DEBUG)
If you observe the crash please do take a bug report. If possible also dump dbinfo for the app's package: adb shell dumpsys dbinfo <package-name>
gr...@tablet.academy
We have gone back to 2.0.0 and haven't been able to make it crash again unfortunately. Will keep trying. We are rolling out an update next week that reverts to 1.0.0 and will let you know if the crash goes away in production as well
va...@google.com
I just want to distinguish between which versions you are using/experiencing this on.
1. The bug title lists 2.0.0
2. The first update lists 2.0.1-rc01
3. #14 lists 2.0.0
Can you reproduce at all with any version of WorkManager 2.x at this point? And if so, which ones work and which ones don't?
1. The bug title lists 2.0.0
2. The first update lists 2.0.1-rc01
3. #14 lists 2.0.0
Can you reproduce at all with any version of WorkManager 2.x at this point? And if so, which ones work and which ones don't?
gr...@tablet.academy
Our store version had 2.0.0 and is what the screenshots come from, we reproduced locally using that. We upgraded to 2.0.1rc1 and the phone was still crashing. We downgraded to 1.0.0 and the crash went away. To help with this testing we went back to 2.0.0 to try and get it to crash again but we haven't been able to get it to happen again.
va...@google.com
We rolled out an update to the Play Store using WorkManager 1.0.0 and the issue has persisted unfortunately
Description
Any app that requests the OAuth scope
*A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.*
This is seen on the API Explorer on the API Reference page at
*What steps will reproduce the problem?*
1. Ensure the user is in a domain/OU with the setting for "Access to additional services without individual control" is set to OFF.
2. Retrieve a list of all classes at
3. Visit
4. Click on EXECUTE and allow access. This will produce the Authorization Error.
*What is the expected output? What do you see instead? If you see error messages, please provide them.*
Expected: Authorisation is accepted and the topics are listed.
Actual: Error below
# Authorization Error
**Error 400: invalid_request**
Account restricted
Learn more
**Request Details**
* response_type=permission id_token
* openid.realm=
* redirect_uri=storagerelay://https/
* client_id=
* ss_domain=
* gsiwebsdk=shim
* access_type=online
* display=page
* scope=
Please provide any additional information below, such as number of users impacted and whether you have been able to find a workaround.
The only workaround I've found is not to use the courses.topics methods.