ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Understand how WorkManager retries can lead to duplicate database writes on Android 13 and what consistency guarantees exist. Uncertainty WorkManager’s retry mechanism uses exponential or linear back‑off but the documentation does not state whether a failed attempt’s side effects are rolled back when the work is retried or cancelled. The UniqueWork API’
WorkManager's documented retry path re-invokes a Worker's doWork() on every attempt, with exponential backoff between runs. Unique work names and ExistingWorkPolicy stop a duplicate work item from being enqueued, but as of the 2.8.x line (worth re-checking against the current release) nothing in the documented API collapses the effects of a retried execution
Goal Confirm whether WorkManager retries a constrained OneTimeWorkRequest immediately after a brief network interruption or defers the attempt until the next scheduled trigger, so low-traffic workloads can estimate wake-up and battery costs accurately. Constraints NetworkOnMainThreadException is documented on API level 11 and above when network code runs on
android