ActivityResultContract returns RESULT_CANCELED after ActivityNotFoundException [200845664]

Fixed

Bug

Status Update

No update yet.

Description

gm...@gmail.com

created issue #1

Sep 23, 2021 02:29PM

Component used: Activity
Version used: 1.3.1, 1.4.0-alpha02
Devices/Android versions reproduced on: API 21-30

Steps to reproduce:

Create custom contract with non-existing action or package.
Catch ActivityNotFoundException as suggested in the docs.
After getting an exception you also get ActivityResult{resultCode=RESULT_CANCELED, data=null}.

Conceptually this violates generic principle of Java/Kotlin that method can throw exception OR return result, but not both.

Practically this complicates implementing different handling for "app not found" vs "user pressed Back button" scenarios.

I understand that this quirk is inherited form old startActivityForResult() mechanism, but if you're trying to build a better API with contracts, maybe it's time to reconsider it.

Comments

il...@google.com <il...@google.com> #2Sep 23, 2021 04:35PM

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

gm...@gmail.com <gm...@gmail.com> #3Sep 23, 2021 08:21PM

Great! Thanks a lot, I'll look for the live updates soon!

TestActivityResult.zip

105 KB

Download

il...@google.com <il...@google.com> Sep 23, 2021 10:27PM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #4Sep 27, 2021 10:35PM

Project: platform/frameworks/support
Branch: androidx-main

commit c4531c406f3b65d2f84821beaf4c106f22ecebf6
Author: Jeremy Woods <jbwoods@google.com>
Date: Thu Sep 23 17:06:56 2021

Don't return a result when throwing

When there is no available activity for a launched
ActivityResultLauncher an ActivityNotFoundException is thrown, but the
underlying startActivityForResult APIs also still return a result with a
RESULT_CANCELLED request code.

We should ensure that when the ActivityResultRegistry's launch throws an
ActivityNotFoundException, we don't also return a result to the
callback.

RelNote: "The `ActivityResultRegistry` will no longer return a result
to the `ActivityResultCallback` when the `launch` call throws any
`Exception`."
Test: added tests
Bug: 200845664

Change-Id: If4f9159bce2edf7f3f0c76e7ff37ce21b05c13ee

M activity/activity/src/androidTest/java/androidx/activity/ComponentActivityResultTest.kt
M activity/activity/src/main/java/androidx/activity/result/ActivityResultRegistry.java

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

jb...@google.com <jb...@google.com> #5Sep 28, 2021 04:18PM

Marked as fixed.

This has been fixed internally and will be released following the Activity 1.4.0-beta01 release.

gm...@gmail.com <gm...@gmail.com> #6Sep 28, 2021 06:53PM

Great news, thanks! :)

ra...@gmail.com <ra...@gmail.com> #7Dec 24, 2021 04:35AM

🙂

md...@gmail.com <md...@gmail.com> #8Feb 13, 2022 05:15PM

git@github.com:google/Accessibility-Test-Framework-for-Android.git

gm...@gmail.com <gm...@gmail.com> #9Jul 7, 2022 01:22PM

Unfortunately, the issue still exists in Jetpack Compose, probably because it uses another overload of ActivityResultRegistry.register().

Sample project attached.

Or should I file a new issue for that?

TestActivityResult2.zip

108 KB

Download

jb...@google.com <jb...@google.com> #10Jul 7, 2022 02:22PM

Please file a new issue.

gm...@gmail.com <gm...@gmail.com> #11Jul 7, 2022 09:12PM

Done

b9...@gmail.com <b9...@gmail.com> #12Aug 17, 2022 04:11AM

Because dispatchResult still get called, I found that if next launch invoke immediately, mLaunchedKeys will add new key then dispatch RESULT_CANCELED. More like race condition.

il...@google.com <il...@google.com> #13Oct 18, 2022 08:26PM

Re comment#12 - I don't think I understand exactly what you are getting at - could you file a new issue with a sample project that exhibits this kind of race condition? We'd love to take a closer look at this.