AGP 7.4.0-alpha09 generates builds that won't upload into Firebase App Distribution [241469653]

Fixed

Bug

Status Update

No update yet.

Description

co...@protonmail.com

created issue #1

Aug 5, 2022 01:59PM

You can see some of my investigation in this thread https://github.com/firebase/firebase-android-sdk/issues/3966

My hypothesis is either AGP 7.4.0-alpha09 has something broken that prevents builds to firebase app distribution OR app distribution needs something changed so that it can handle these builds.

I do not have a minimal repro project. Everytime I try to prune down my companys project, the uploads to firebase work again.

What I can say for certain is that if I switch from AGP 7.4.0-alpha09 to AGP 7.3.0-beta05, then everything works. If I move back to AGP 7.4.0-alpha09 then I can't upload into firebase app dist BUT I can upload to play store. I'm generating apks (not bundles) in all cases as I have not switched to aabs yet.

To continue my research I'm going to try to go from alpha01 to alpha09 and see which one breaks.

Comments

co...@protonmail.com <co...@protonmail.com> #2Aug 5, 2022 02:59PM

This happens to me when using pattern+fingerprint on api 29 using 1.0.1

uc...@google.com <uc...@google.com> Aug 8, 2022 05:39AM

Assigned to an...@google.com.

je...@google.com <je...@google.com> #3Aug 8, 2022 09:46PM

Reassigned to sp...@google.com.

happens to me on Android P using 1.0.1

sp...@google.com <sp...@google.com> #4Aug 8, 2022 11:20PM

Is there any workaround for this? Can we expect this to be fixed?

co...@protonmail.com <co...@protonmail.com> #5Aug 8, 2022 11:22PM

I am facing the same problem too! Is there any solution to this problem?

co...@protonmail.com <co...@protonmail.com> #6Aug 8, 2022 11:46PM

Still seeing this issue on Android 10 Pixel 4.

Message last modified on Aug 8, 2022 11:46PM

co...@protonmail.com <co...@protonmail.com> #7Aug 8, 2022 11:51PM

Our team is facing this issue as well. What are the alternatives available right now apart from cloning the library and changing the behavior?

sp...@google.com <sp...@google.com> #8Aug 9, 2022 04:43PM

Biometric prompt is also not dismissed if user goes to different apps on API levels below 29. The same behavior is not true for API 29 and above. Is there any workaround for this?

co...@protonmail.com <co...@protonmail.com> #9Aug 9, 2022 04:58PM

Same issue for me. API 10 device during Fingerprint prompt.

sp...@google.com <sp...@google.com> #10Aug 9, 2022 05:03PM

162013003

co...@protonmail.com <co...@protonmail.com> #11Aug 9, 2022 05:06PM

Have the same problem, Android 10, Mi 9T

sp...@google.com <sp...@google.com> #12Aug 9, 2022 05:20PM

Also happening with 1.2.0-alpha04.

co...@protonmail.com <co...@protonmail.com> #13Aug 11, 2022 06:52PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Hao Dong <spdonghao@google.com>
Link: https://android-review.googlesource.com/3343432

Propogate cancel authentication in onStop() for all api levels.

Expand for full commit details

Propogate cancel authentication in onStop() for all api levels. 
 
Bug: 149770989 
Test: ./gradlew biometric:biometric:assemble 
 
Change-Id: I8c393f400d60f2b2af075671c4cf2727e63d82b8

Files:

M biometric/biometric/src/main/java/androidx/biometric/BiometricFragment.java

Hash: 302fab7c34832a989f434e43f16b146d37fa08b6
Date: Wed Nov 13 02:45:59 2024

sp...@google.com <sp...@google.com> #14Aug 11, 2022 06:58PM

Status: Won't Fix (Not Reproducible)

Thanks for looking into it!

I agree it's strange they have an implementation dependency on junit, and I'm glad they're removing it in okhttp 5+.

I'll go ahead and close this bug for now.

sp...@google.com <sp...@google.com> Oct 28, 2022 06:19PM

Status: Assigned (reopened)

sp...@google.com <sp...@google.com> #15Nov 1, 2022 04:48PM

Marked as fixed.

This is fixed by Change-Id: I12ec8785cd4dbb6e523c66b4620ed2388f448822, which will be in AGP 7.4.0-rc01 and 8.0.0-alpha08.

sp...@google.com <sp...@google.com> #16Nov 1, 2022 04:50PM

Thanks for filing the bug, OP. Your observation in comment #2 that alpha07 was the first broken version helped me find the root cause.

co...@protonmail.com <co...@protonmail.com> #17Nov 2, 2022 08:30AM

FUCK YEAH! Glad I was helpful! Appreciate you working through it with me here. Cheers. Once I update to alpha08 I will remove the workaround I added. cheers