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

This seems to be occurring in the two latest versions of the Android Gradle plugin, specifically in 3.3.0-beta04 and 3.4.0-alpha04. Caused by the complete deprecation of a method used by the Safe Args plugin (see ag/5426837). I'll check with the tools team to see what can Safe-Args do about change.

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

Marked as fixed.

Some news about this bug ?

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

A fix for this issue will be available in alpha09

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

For exact reference, this was fixed in

https://android-review.googlesource.com/845025

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

Am using alpha09 here (had been seeing issue mentioned above before updating)....but not getting following during gradle sync. I'm using Android Studio 3.4 Canary 9 (but also had same problem using 3.3 RC3)

Caused by: kotlin.TypeCastException: null cannot be cast to non-null type org.gradle.api.resources.TextResource
at androidx.navigation.safeargs.gradle.SafeArgsPlugin.setApplicationId(SafeArgsPlugin.kt:87)
at androidx.navigation.safeargs.gradle.SafeArgsPlugin.access$setApplicationId(SafeArgsPlugin.kt:39)
at androidx.navigation.safeargs.gradle.SafeArgsPlugin$apply$1$task$1.execute(SafeArgsPlugin.kt:63)
at androidx.navigation.safeargs.gradle.SafeArgsPlugin$apply$1$task$1.execute(SafeArgsPlugin.kt:39)
at org.gradle.api.internal.tasks.DefaultTaskContainer.create(DefaultTaskContainer.java:360)
at androidx.navigation.safeargs.gradle.SafeArgsPlugin$apply$1.invoke(SafeArgsPlugin.kt:59)
at androidx.navigation.safeargs.gradle.SafeArgsPlugin$apply$1.invoke(SafeArgsPlugin.kt:39)
at androidx.navigation.safeargs.gradle.SafeArgsPluginKt$sam$org_gradle_api_Action$0.execute(SafeArgsPlugin.kt)
at org.gradle.internal.ImmutableActionSet$SingletonSet.execute(ImmutableActionSet.java:225)
at org.gradle.api.internal.DefaultDomainObjectCollection.doAdd(DefaultDomainObjectCollection.java:247)
at org.gradle.api.internal.DefaultDomainObjectCollection.add(DefaultDomainObjectCollection.java:236)
at com.android.build.gradle.LibraryExtension.addVariant(LibraryExtension.java:93)
at com.android.build.gradle.FeatureExtension.addVariant(FeatureExtension.java:121)
at com.android.build.gradle.internal.ApiObjectFactory.create(ApiObjectFactory.java:134)

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

that should read - "but now getting following...."1

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

We are aware of the error mentioned in #6, see

https://issuetracker.google.com/issues/121304903

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.