android / android/codelab-android-workmanager
Receiver not registered
- Dominant language
- Kotlin
- Stars
- 557
- Forks
- 242
- PR merge metrics
- No merged PRs in 30d
Description
Fatal Exception: java.lang.IllegalArgumentException: Receiver not registered: androidx.work.impl.constraints.trackers.NetworkStateTracker$NetworkStateBroadcastReceiver@e94f739
at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:862)
at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1355)
at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:576)
at androidx.work.impl.constraints.trackers.NetworkStateTracker.stopTracking(NetworkStateTracker.java:125)
at androidx.work.impl.constraints.trackers.ConstraintTracker.removeListener(ConstraintTracker.java:86)
at androidx.work.impl.constraints.controllers.ConstraintController.replace(ConstraintController.java:97)
at androidx.work.impl.constraints.WorkConstraintsTracker.replace(WorkConstraintsTracker.java:106)
at androidx.work.impl.background.greedy.GreedyScheduler.removeConstraintTrackingFor(GreedyScheduler.java:222)
at androidx.work.impl.background.greedy.GreedyScheduler.onExecuted(GreedyScheduler.java:208)
at androidx.work.impl.Processor.onExecuted(Processor.java:304)
at androidx.work.impl.Processor$FutureListener.run(Processor.java:377)
at android.os.Handler.handleCallback(Handler.java:743)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:150)
at android.app.ActivityThread.main(ActivityThread.java:5665)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:822)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:712)
Contributor guide
Research direction
Start by reproducing the IllegalArgumentException and trace the call path from GreedyScheduler.onExecuted through ConstraintTracker.removeListener to NetworkStateTracker.stopTracking. Inspect the referenced WorkManager classes and Android receiver lifecycle; done means the reported crash no longer occurs during constraint tracking cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100