Status Update
Comments
ap...@google.com <ap...@google.com> #2
Is this fixed? I'm still seeing this issue with AGP 8.1.0-beta01 + Gradle 8.1
pe...@gmail.com <pe...@gmail.com> #4
Due to this bug in CI we hit configuration cache invalidation 100% of the time. Can we make sure the fix lands soon? And especially before 8.1.0 stable.
jb...@google.com <jb...@google.com> #5
I cc'ed you on the CL which should be landed this week.
ba...@gmail.com <ba...@gmail.com> #6
Aurimas, is this 8.1 blocking for Androidx? If not, feel free to remove the "Blocking release" label.
ba...@gmail.com <ba...@gmail.com> #7
am...@gmail.com <am...@gmail.com> #9
Reassigning to Xav to review CP to 8.1 branch
wa...@gmail.com <wa...@gmail.com> #10
Scott, do we have a cherry-pick ready for the lint fix?
re...@gmail.com <re...@gmail.com> #11
Yes, Change-Id: I994677cebb63de5472bb8ea561bdad0336c72f55
ku...@gmail.com <ku...@gmail.com> #12
ow...@gmail.com <ow...@gmail.com> #13
Hey Saurabh, ag/I994677cebb63de5472bb8ea561bdad0336c72f55 still needs DrNo approval. Can you give approval, or can you reassign to someone who can?
jb...@google.com <jb...@google.com> #14
I still see it being broken in AGP 8.2.0-alpha15.
See me trying to remove the entry from the allow list:
Description
Much like was done for Fragments in b/162255449 , When using the ActivityResultRegistry with a
LifecycleOwner
, the latest possible time thatregister()
should be called is while the lifecycle is CREATED. This ensures that any registered callbacks are always registered in the same exact order.If there is an attempt to register after the
LifecycleOwner
is STARTED, we should throw.This is different from b/162255449 because fragments don't move their Lifecycle until after their lifecycle callbacks (another joy of the multiple fragment lifecycles). Once b/127528777 is fixed, this will go for fragments as well.