| commit | 4b425712c6a777148af767cb30240d632c51f55b | [log] [tgz] |
|---|---|---|
| author | Christopher Tate <ctate@google.com> | Mon Jun 27 16:12:41 2016 -0700 |
| committer | Christopher Tate <ctate@google.com> | Mon Jun 27 16:12:41 2016 -0700 |
| tree | 93b81213677551afc668e7d01a73965b3747a29f | |
| parent | d9069f8c9e24f5c8d9af0017f1474063022af367 [diff] |
Fix #29737133 : content-trigger jobs not running properly When removing the ContentObserver wrapper from our internal bookkeeping we were using the wrong key. That led to future re-registrations thinking they were reusing a currently- registered observers, but instead never getting onChange() notifications. Change-Id: Id3111db057ae63194049d7d48d45b75be6bb0000