Credential selection UI not showing if device has more then 6 google account log in [355141766]

Assigned

Bug

Status Update

No update yet.

Description

mu...@yolo.com

created issue #1

Jul 24, 2024 12:24PM

Component used: Credentials

Version used:

Devices/Android versions reproduced on:
Samsung SM-S908B
Android 14

Sample project :

https://github.com/android/identity-samples/tree/main/CredentialManager/app

Logs
failure launching com.android.credentialmanager/.CredentialSelectorActivity, giving up
android.os.TransactionTooLargeException: data parcel size 525508 bytes
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:586)
at android.app.IApplicationThread$Stub$Proxy.scheduleTransaction(IApplicationThread.java:2014)
at android.app.servertransaction.ClientTransaction.schedule(ClientTransaction.java:230)
at com.android.server.wm.ClientLifecycleManager.scheduleTransaction(ClientLifecycleManager.java:67)
at com.android.server.wm.ClientLifecycleManager.onClientTransactionItemScheduled(ClientLifecycleManager.java:234)
at com.android.server.wm.ClientLifecycleManager.scheduleTransactionAndLifecycleItems(ClientLifecycleManager.java:153)
at com.android.server.wm.ActivityTaskSupervisor.realStartActivityLocked(ActivityTaskSupervisor.java:959)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.test(RootWindowContainer.java:3807)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.test(RootWindowContainer.java:3758)
at com.android.server.wm.ActivityRecord.forAllActivities(ActivityRecord.java:4868)
at com.android.server.wm.WindowContainer.forAllActivities(WindowContainer.java:1832)
at com.android.server.wm.WindowContainer.forAllActivities(WindowContainer.java:1826)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.accept(RootWindowContainer.java:3795)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.accept(RootWindowContainer.java:3758)
at com.android.server.wm.Task.forAllRootTasks(Task.java:3243)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2213)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2213)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2213)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2213)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2213)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2213)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2206)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.process(RootWindowContainer.java:3774)
at com.android.server.wm.RootWindowContainer.attachApplication(RootWindowContainer.java:1856)
at com.android.server.wm.ActivityTaskManagerService$LocalService.attachApplication(ActivityTaskManagerService.java:6658)
at com.android.server.am.ActivityManagerService.finishAttachApplicationInner(ActivityManagerService.java:4931)
at com.android.server.am.ActivityManagerService.finishAttachApplication(ActivityManagerService.java:5033)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2783)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2822)
at android.os.Binder.execTransactInternal(Binder.java:1500)
at android.os.Binder.execTransact(Binder.java:1444)
Process com.android.credentialmanager (pid 25782) has died: cch+5 CEM

Comments

bl...@google.com <bl...@google.com> #2Jul 24, 2024 12:33PM

Reassigned to ak...@google.com.

Automated by Blunderbuss job android-credential-manager-autoassigner for config android_credman_config for component 1301097.

ar...@google.com <ar...@google.com> #3Jul 24, 2024 01:15PM

Reassigned to ar...@google.com.

The error you posted state "activity is cancelled by the user". This implies the request was cancelled somehow during the request.

Can you grab a bugreport and attach it to this bug?

ar...@google.com <ar...@google.com> #4Jul 24, 2024 01:49PM

Hi Muhammad, this is a know issue and we are actively working towards the solution. Timelines are Q3 end.

Although, this would be a rare usecase as not all users have these much google accounts. Let us know if your app has any specific scenario where you need to cater this case on an urgent basis.

mu...@yolo.com <mu...@yolo.com> #5Jul 24, 2024 01:54PM

Hi,

Thank you for the prompt response. I agree its a rare case but some users have bunch of accounts in their devices. its really an issue for us because its the entry point of our application.

ar...@google.com <ar...@google.com> #6Jul 24, 2024 04:01PM

yeah we are working on it and trying to resolve soon, will keep you posted

fr...@gmail.com <fr...@gmail.com> #7Oct 15, 2024 12:40AM

It's October, this was reported in July. What's the holdup on fixing this issue? I get it we're all humans and we make mistakes, but this is unacceptable on such a critical piece.

ar...@google.com <ar...@google.com> Oct 15, 2024 04:34AM

Reassigned to re...@google.com.

lh...@google.com <lh...@google.com> #8Oct 15, 2024 04:58PM

Fix is planned for the 25Q2 Android release. This is being tracked by internal issue:

b/354633197

fr...@gmail.com <fr...@gmail.com> #9Oct 16, 2024 08:20PM

Ok now I'm confused. How is this related to the Android framework release when this is an Androidx library? Unless you're planning to increase the binder limit on the 25Q2 that won't fix the issue for all users in older Android versions. Can you elaborate a bit more? Thank you.

re...@google.com <re...@google.com> #10Dec 4, 2024 12:02AM

Androidx library is a client library used by apps. We depend on the android framework for part of the core functionality of credential manager.

ph...@bitwarden.com <ph...@bitwarden.com> #11Dec 9, 2024 09:05PM

I know this is already being addressed, but wanted to note it can also be replicated in a Credential Provider application. When there are several results in the library responses, `CreateCredentialResponse` and `BeginGetCredentialResponse`, we see the same "TransactionTooLarge" exception in logs and the RP never receives the response. The issue becomes more frequent and with fewer results when custom icons are used. The user is often left with the RP's loading indicator spinning indefinitely and no indication a failure occurred.

If the Credential Provider application supports multiple user accounts, each user account may have different credentials saved for the same site or application. This makes showing potential matches from all of the user's accounts very unreliable, regardless of the result size. We have been able to reproduce the exception starting with `androidx.credentials:1.5.0-alpha05` thru `1.5.0-beta01`. Please consider raising the priority of this issue, especially with `androidx.credentials:1.5.0` nearing production release.