Canceling registration modal throws ConstraintError [271863184]

Fixed

Bug

Status Update

No update yet.

Description

va...@shopify.com

created issue #1

Mar 7, 2023 12:04AM

Component used: Credentials

Version used: 1.0.0-alpha03

Devices/Android versions reproduced on: Huawei P30 Pro (VOG-L29)

I have multiple Google accounts on my phone. After triggering the passkey registration modal, I pressed the "Cancel" button and I got a CreatePublicKeyCredentialDomException with ConstraintError instead of the expected CreateCredentialCancellationException

Here are some logs (PasskeyUtils is from my application):

03-06 18:59:09.005 19307 19307 I Fido    : [AuthenticateChimeraActivity] FIDO2 operation is called from com.shopify.arrive.debug [CONTEXT service_id=287 ]
03-06 18:59:09.007 19307 19307 I Fido    : [AuthenticateViewModel] Determining the attachment [CONTEXT service_id=287 ]
03-06 18:59:09.017 19307 19307 I Fido    : [AuthenticateChimeraActivity] onAttachmentUpdate [CONTEXT service_id=287 ]
03-06 18:59:09.018 19307 19385 I Fido    : [AuthenticateViewModel] StrongBox not needed. [CONTEXT service_id=287 ]
03-06 18:59:09.020 19307 19307 I Fido    : [AuthenticateChimeraActivity] Using default UserVerifier. [CONTEXT service_id=287 ]
03-06 18:59:09.023 19307 19307 I Fido    : [StringStoreKeyHandleCache] initU2fDeviceCache
03-06 18:59:09.023 19307 19307 I Fido    : [FidoApiImpl] updateTransaction is called for resume
03-06 18:59:09.099  1508  5553 I ActivityManager: Process com.huawei.skytone (pid 25789) has died: svcb SVC
03-06 18:59:09.099  1508  5553 W ActivityManager: Scheduling restart of crashed service com.huawei.skytone/com.huawei.android.vsim.service.VSimService in 1000ms
03-06 18:59:09.248 19307 19384 I Fido    : [RegistrationRequestHandler] Registering key via credential store.
03-06 18:59:09.304 19307 19307 I Fido    : [PasskeysCreationFragment] PasskeysCreationFragment is shown [CONTEXT service_id=287 ]
03-06 18:59:10.897 19307 19384 I Fido    : [RequestController] Timeout Runnable is removed, and timer is stopped.
03-06 18:59:10.901 19307 19384 I Fido    : [RequestController] Timeout Runnable is removed, and timer is stopped.
03-06 18:59:10.915 19307 19307 I Fido    : [FidoApiImpl] updateTransaction is called for pause
03-06 18:59:10.915 19307 19307 E Fido    : [FidoApiImpl] pauseSecurityKeyRequestController should not be called when SecurityKeyRequestController is null.
03-06 18:59:10.957 31580 31580 D PasskeyUtils: error:androidx.credentials.exceptions.publickeycredential.CreatePublicKeyCredentialDomException: Unable to get sync account.
03-06 18:59:10.957 31580 31580 D PasskeyUtils: domError:androidx.credentials.exceptions.domerrors.ConstraintError@8d8d7a9
03-06 18:59:10.979 19307 19307 I Fido    : [FidoApiImpl] updateTransaction is called for stop
03-06 18:59:10.979 19307 19307 E Fido    : [FidoApiImpl] finishSecurityKeyRequestController should not be called when SecurityKeyRequestController is null.

Comments

he...@google.com <he...@google.com> #2Mar 7, 2023 12:43AM

Reassigned to he...@google.com.

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ap...@google.com <ap...@google.com> #3Mar 7, 2023 05:07AM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

he...@google.com <he...@google.com> #4Mar 7, 2023 07:37PM

Marked as fixed.

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

pr...@google.com <pr...@google.com> #5Mar 22, 2023 08:23PM

Experiencing the same issues, please see my other report for any useful logs:

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

sh...@gmail.com <sh...@gmail.com> #6Mar 23, 2023 07:52AM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

va...@shopify.com <va...@shopify.com> #7Mar 25, 2023 12:57AM

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do

va...@shopify.com <va...@shopify.com> #8Apr 4, 2023 05:20PM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

he...@google.com <he...@google.com> #9Apr 4, 2023 09:26PM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.

va...@shopify.com <va...@shopify.com> #10Apr 4, 2023 10:01PM

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

he...@google.com <he...@google.com> #11Apr 4, 2023 10:02PM

@comment#9 The Play Store will eventually require targeting API 33, then 34, etc, so accepting this regression in a customer release would be a time ticking bomb for Wear OS apps.

Thank you for the update @comment#10