Fixed
Status Update
No update yet.
Comments
ap...@google.com
I am able to also reproduce issue #1 now; I've committed a change to the sample project that sets enableMultiInstanceInvalidation() on the DB and adjusts the timing a bit more. After running it for 15 minutes or so I am seeing multiple skipped updates.
My production app uses enableMultiInstanceInvalidation() as well, so this may be a significant factor.
jb...@google.com
Any thoughts on this one? I mean, it makes JournalMode.TRUNCATE largely useless, unless one has a penchant for random app misbehaviors. I'd like to keep using TRUNCATE, as it avoids certain headaches from WRITE_AHEAD_LOGGING.
Description
Component used: Activity Version used: 1.2.0-alpha07
If you register for a result with a
LifecycleOwnerand your activity goes through process death and restoration, once it is created again if there is already result a waiting to be returned to theLifecycleOwneran observer is added to wait until theLifecycleisSTARTED. When the lifecycle owner is unregistered, the observer is never removed.We should keep track of any observers added to the
LifecycleOwnerand remove them if the callback for the lifecycle owner is ever unregistered.