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
When using the ActivityResultAPIs with fragment, the latest possible time that
registerForActivityResult()should be called is inonCreate(). Any calls made toregisterForActivityResult()made afteronCreate()will be ignored.Instead of ignoring these calls and allowing developers to assume that their callback is registered, we should throw an exception notifying that they are attempting to register too late.