History log of /frameworks/support/work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/ConstraintProxyUpdateReceiver.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
697d6a4a3797bc71d0dd8685937a318e9934066b 17-Apr-2018 Rahul Ravikumar <rahulrav@google.com> Use the standard Android (android.util.Log) logger.

- Rename Logger to InternalLogger so we can start adding internal only
logs.
- Remove redundant logs in AlarmManager based implementation.

Test: Existing tests pass.
Change-Id: I44babc42dafbce0311f439ffaca6bf40fc058be0
/frameworks/support/work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/ConstraintProxyUpdateReceiver.java
a61486ba821b96e94a3b7631c26c33e6e6aa059b 12-Mar-2018 Rahul Ravikumar <rahulrav@google.com> Removes the possibility for stuck broadcast queues.

- Updating constraint proxies now happens via a designated broadcast receiver.
- This is to prevent the possiblity of an App ANR + PackageManager#setComponentEnabledSetting(false) from blocking
the global broadcast queue.
- The broadcast receiver being used is *not* exported, and thus should not effect the global broadcast queue.

Test: Unit tests pass. Also ran integration tests.
Change-Id: I97fb279dd7a01cfa2f6a9c51d0eb92d62c842ed3
Fixes: b/73549299
Original bug fixed in O-MR1 (b/64854337).
/frameworks/support/work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/ConstraintProxyUpdateReceiver.java