Fixed
Status Update
Comments
my...@gmail.com <my...@gmail.com> #2
Relevant logcat:
W ActivityManager: Unable to start service Intent { cmp=<pkgname>/androidx.room.MultiInstanceInvalidationService } U=0: not found
Because room never checks for bindService results (I assume it returns false), MultiInstanceInvalidationClient is never put into effect when room database is built when in lockdown.
W ActivityManager: Unable to start service Intent { cmp=<pkgname>/androidx.room.MultiInstanceInvalidationService } U=0: not found
Because room never checks for bindService results (I assume it returns false), MultiInstanceInvalidationClient is never put into effect when room database is built when in lockdown.
da...@google.com <da...@google.com> #4
A version of Room is scheduled to be released around Feb 20, but your change missed that train, so it might be a bit before a fix for this reaches the public.
Description
Version used: 2.2.3
Devices/Android versions reproduced on: N/A
MultiInstanceInvalidationService does not have android:directBootAware="true" in manifest. This might make direct boot aware applications not be able to use multi-instance invalidation while in lockdown mode.