Fixed
Status Update
Comments
ra...@google.com <ra...@google.com>
ap...@google.com <ap...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-main
commit 90e47433bf5d976e1204029092b8fa0916136fef
Author: Rahul Ravikumar <rahulrav@google.com>
Date: Fri Dec 25 14:07:42 2020
Mark the outer transaction as successful.
* While this is not a bug in itself, some Motorola devices don't deal
with this very well and this causes native SQLite crashes.
Test: All existing tests pass.
Fixes: b/175944460
Change-Id: I58127dd514aaabfccee1dd8463fd61cb00500b04
M work/workmanager/src/main/java/androidx/work/impl/WorkerWrapper.java
https://android-review.googlesource.com/1535368
Branch: androidx-main
commit 90e47433bf5d976e1204029092b8fa0916136fef
Author: Rahul Ravikumar <rahulrav@google.com>
Date: Fri Dec 25 14:07:42 2020
Mark the outer transaction as successful.
* While this is not a bug in itself, some Motorola devices don't deal
with this very well and this causes native SQLite crashes.
Test: All existing tests pass.
Fixes:
Change-Id: I58127dd514aaabfccee1dd8463fd61cb00500b04
M work/workmanager/src/main/java/androidx/work/impl/WorkerWrapper.java
ac...@gmail.com <ac...@gmail.com> #4
Which work manager release will include this fix?
ra...@google.com <ra...@google.com> #5
2.5.0-rc01
will have it, once available.
ac...@gmail.com <ac...@gmail.com> #6
Thanks. Picked up the new workmanager build and no more issue happens again on Motorola devices.
Description
Version used: all version including 2.5.0-rc01
Devices/Android versions reproduced on: Motorola G 7.0 (SDK 24), 7.1 (SDK 25)
Related source code:
mWorkDatabase.setTransactionSuccessful() must be called after calling resolve(true) line 193. Nested transactions will be rolled back if the outer transaction isn't marked as successful.
This behavior causes crashes on Motorola devices with 7.0/7.1
See crash report from Google Play for Motorola devices.