You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specify the language of the codelab if it is not English:
In which task and step of the codelab can this issue be found?
9. Debug WorkManager with Background Task Inspector
Describe the problem
As described in the codelab, the workers can be seen in Background Task Inspector "Workers" Tab
But I can't see any workers. I can only see Jobs.
Should I config something in Android Studio?
Steps to reproduce?
Go to...
Click on...
See error...
Versions Android Studio version:Electric Eel 2022.1.1 and 2022.1.1 Patch 1 API version of the emulator:31.3.15
Additional information Include screenshots if they would be useful in clarifying the problem.
The text was updated successfully, but these errors were encountered:
simonzhang98
changed the title
Codelab: Advanced WorkManager and Testing
No workers in Background Task Inspector, only jobs
Feb 2, 2023
URL of codelab
https://developer.android.google.cn/codelabs/basic-android-kotlin-compose-verify-background-work?continue=https%3A%2F%2Fdeveloper.android.google.cn%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-7-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-verify-background-work#8
Specify the language of the codelab if it is not English:
In which task and step of the codelab can this issue be found?
9. Debug WorkManager with Background Task Inspector
Describe the problem
As described in the codelab, the workers can be seen in Background Task Inspector "Workers" Tab
But I can't see any workers. I can only see Jobs.
Should I config something in Android Studio?
Steps to reproduce?
Versions
Android Studio version: Electric Eel 2022.1.1 and 2022.1.1 Patch 1
API version of the emulator: 31.3.15
Additional information
Include screenshots if they would be useful in clarifying the problem.
The text was updated successfully, but these errors were encountered: