Throw error when attempting to registerForActivityResult after CREATED [165435866]

Fixed

Bug

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Aug 19, 2020 03:09AM

Much like was done for Fragments in b/162255449, When using the ActivityResultRegistry with a LifecycleOwner, the latest possible time that register() 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.

Comments

ap...@google.com <ap...@google.com> #2Sep 1, 2020 08:10PM

Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

jb...@google.com <jb...@google.com> #3Sep 1, 2020 09:05PM

Marked as fixed.

This functionality has been added in wear:1.1.0-alpha01

https://developer.android.com/jetpack/androidx/releases/wear#1.1.0-alpha01

pe...@gmail.com <pe...@gmail.com> #4Oct 9, 2020 11:43AM

God bless you, unknown Google developer.

jb...@google.com <jb...@google.com> #5Oct 9, 2020 04:59PM

Based on

comment#3

. Closing this issue as fixed.

ba...@gmail.com <ba...@gmail.com> #6Nov 6, 2020 08:17PM

The resolution to this issue means that Composable functions can no longer call activity.registerForActivityResult() via user interaction.

Is this intentional, and if so, what is the solution?

ba...@gmail.com <ba...@gmail.com> #7Nov 6, 2020 08:18PM

Maybe I should clarify that by "Composable functions" I of course mean functions with the @Composable flag created using Jetpack Compose.

il...@google.com <il...@google.com> #8Nov 6, 2020 08:26PM

Re #6 - You should be using the ActivityResultRegistry's register() method that does not take a LifecycleOwner from a composable (as you must manually tie the register and unregister calls to onCommit and onDispose). That method is unaffected by these changes.

am...@gmail.com <am...@gmail.com> #9Mar 25, 2021 01:56PM

Re #8 - Thanks. This fixed my issues.

I have a dynamic ui Screen that rendered based on the response. and this solved it.

wa...@gmail.com <wa...@gmail.com> #10Nov 17, 2021 02:30PM

My phone is hacked ..what should I do will I start to pay a fresh

re...@gmail.com <re...@gmail.com> #11Oct 13, 2022 01:33AM

promote:

https://posts.google.com/url?q=https://rekart.live

ku...@gmail.com <ku...@gmail.com> #12Sep 9, 2023 01:29PM

Comment has been deleted.

Message last modified on Sep 9, 2023 01:29PM

ow...@gmail.com <ow...@gmail.com> #13Sep 19, 2023 02:51AM

So this update completely broke our ability to launch a file picker on button click as the function to invoke the file picker is in an entirely different class and by the time it's invoked is going to just kill the app. Not really sure what the actual logic was here.

jb...@google.com <jb...@google.com> #14Sep 19, 2023 02:14PM

Please see #8.