credentialManager.getCredential() API Suspends Indefinitely on Samsung Galaxy S22, Popup Not Displayed [341690734]

Assigned

Bug

Status Update

No update yet.

Description

gu...@nextstack.org

created issue #1

May 21, 2024 06:15AM

On the Samsung Galaxy S22 device that has 10 Google accounts, the credentialManager.getCredential() API fails to emit any results and suspends the coroutine indefinitely, preventing the sign-in popup from appearing. This issue does not occur on other devices or on another Samsung S22 device with only one Google account, where the same code works as expected.

Reproduction Steps:

1. Use the following code snippet in an Android project:
coroutineScope.launch {
try {
val result = credentialManager.getCredential(
context = activityContext,
request = getCredRequest
)
handleSignIn(result)
} catch (e: GetCredentialException) {
handleFailure(e)
}
}

2. Run the app on a Samsung Galaxy S22 device.
3. Attempt to trigger the credential retrieval process.

Expected Behavior:
The credentialManager.getCredential() method should emit a result and display the sign-in popup.

Actual Behavior:
The coroutine scope is suspended indefinitely, and the sign-in popup does not appear.

Affected Device:
Device Model: Samsung Galaxy S22
Android Version: 14

Working Devices:
Google Pixel 6a (Android 14), Samsung Galaxy S22 Ultra (Android 12), Samsung Galaxy S20 (Android 11), another Samsung Galaxy S22 device (Android 14), Samsung Galaxy Z Fold 3 (Android 12), Samsung Galaxy Z Fold 5 (Android 14)

Comments

vi...@google.com <vi...@google.com> #2May 21, 2024 02:31PM

Assigned to vi...@google.com.

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

gu...@nextstack.org <gu...@nextstack.org> #3May 22, 2024 07:19AM

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?

[Deleted User] <[Deleted User]> #4May 22, 2024 08:09AM

Please find a screencast containing two app actions at the following Google Drive link: (

https://drive.google.com/drive/folders/1-crJp2XUFynqZc5cfGSKO-oZNwdeKd6y?usp=sharing ). In the first app, which is our test app, the sign-in popup appears correctly. However, in the second app, which is our production version, the sign-in popup never appears.

gu...@nextstack.org <gu...@nextstack.org> #5May 22, 2024 11:07AM

I forgot to mention that the build number is UP1A.231005.007.5901EXXS8DXD2.

f....@gmail.com <f....@gmail.com> #6May 27, 2024 10:57AM

I am experiencing the same issue. This seems to happen only with GetGoogleIdOption and not GetSignInWithGoogleOption. It also just happens on phones with a lot of accounts and when I have the setFilterByAuthorizedAccounts = false.

As soon as I credentialManager.getCredential(), the following exception is thrown:

Second failure launching com.android.credentialmanager/.CredentialSelectorActivity, giving up (Ask Gemini)
android.os.TransactionTooLargeException: data parcel size 609076 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:1977)
at android.app.servertransaction.ClientTransaction.schedule(ClientTransaction.java:178)
at com.android.server.wm.ClientLifecycleManager.scheduleTransaction(ClientLifecycleManager.java:65)
at com.android.server.wm.ClientLifecycleManager.scheduleTransactionAndLifecycleItems(ClientLifecycleManager.java:143)
at com.android.server.wm.ActivityTaskSupervisor.realStartActivityLocked(ActivityTaskSupervisor.java:956)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.test(RootWindowContainer.java:3805)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.test(RootWindowContainer.java:3755)
at com.android.server.wm.ActivityRecord.forAllActivities(ActivityRecord.java:4743)
at com.android.server.wm.WindowContainer.forAllActivities(WindowContainer.java:1831)
at com.android.server.wm.WindowContainer.forAllActivities(WindowContainer.java:1825)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.accept(RootWindowContainer.java:3793)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.accept(RootWindowContainer.java:3755)
at com.android.server.wm.Task.forAllRootTasks(Task.java:3198)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2212)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2212)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2212)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2212)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2212)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2212)
at com.android.server.wm.WindowContainer.forAllRootTasks(WindowContainer.java:2205)
at com.android.server.wm.RootWindowContainer$AttachApplicationHelper.process(RootWindowContainer.java:3771)
at com.android.server.wm.RootWindowContainer.attachApplication(RootWindowContainer.java:1858)
at com.android.server.wm.ActivityTaskManagerService$LocalService.attachApplication(ActivityTaskManagerService.java:6582)
at com.android.server.am.ActivityManagerService.finishAttachApplicationInner(ActivityManagerService.java:4904)
at com.android.server.am.ActivityManagerService.finishAttachApplication(ActivityManagerService.java:5006)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2750)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2798)
at android.os.Binder.execTransactInternal(Binder.java:1496)
at android.os.Binder.execTransact(Binder.java:1440)

It seems that there is too much data passing on with the Bundle when there are too many accounts linked to the device.

sg...@google.com <sg...@google.com> May 29, 2024 09:59PM

Reassigned to re...@google.com.

ma...@gmail.com <ma...@gmail.com> #7Jun 11, 2024 01:18PM

I have the exact same issue (and when calling createCredential() ) on my Pixel 8 Pro running Android 15 (build API31.240426.023.B4)

da...@theswing.co.kr <da...@theswing.co.kr> #8Jun 21, 2024 05:34AM

I have the exact same issue

ti...@gmail.com <ti...@gmail.com> #9Jul 2, 2024 01:07AM

I have the exact same issue (and when calling createCredential() )

1. androidx.credentials:credentials : 1.2.2 / 1.3.0-beta02 / 1.5.0-alpha02 => all version have issue

2. While the number of Google accounts logged in varies from device to device, issues arise when the parcel size is exceeded.
3. When an issue occurs, the process is killed, and we do not receive an error response, leading to an indefinite waiting state.
=>Killing 12115.android.credentialmanager/u0a474 (adj -10000): error during init

Request
1. Even if the parcel size exceeds the limit, the UI should still be displayed properly.
2. When an error occurs during UI invocation, the exception should be detected, and an error response should be provided to us.

We request a prompt fix and deployment.
Additionally, we expect guidance on how to resolve this issue in the official release version 1.2.2.

ti...@gmail.com <ti...@gmail.com> #10Jul 2, 2024 03:01AM

After testing on multiple devices, my findings are as follows:
OS Version Below 14 : Success (androidx.credentials.playservices.HiddenActivity displayed)
14 and above : Fail (com.android.credentialmanager/.CredentialSelectorActivity display fail)
*Issues occur depending on the number of Google accounts.(5 ~ 10 Google accounts)

Please resolve this issue quickly.!!!!!!!!!!!

mu...@yolo.com <mu...@yolo.com> #11Jul 24, 2024 12:26PM

I have also same issue
Second 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

jm...@gmail.com <jm...@gmail.com> #12Aug 29, 2024 05:28AM

I am also experiencing this issue on my Android test device, which has multiple Google accounts that I cannot remove. Is there a temporary workaround that would allow me to continue development? When can a fix for this be expected?

si...@gmail.com <si...@gmail.com> #13Sep 28, 2024 05:27PM

Same happens with me.
No error, no popup, tested with GetGoogleIdOption with
filterByAuthorizedAccounts = false as only Option

Google Pixel 7a, Android 14.
Kernel: 5.10.198-android13-4-00050-g12f3388846c3-ab11920634
#1 Mon Jun 3 20:51:42 UTC 2024

Build number: AP2A.240905.003

re...@google.com <re...@google.com> #14Oct 2, 2024 09:37PM

This is to be fixed in Android B

go...@gmail.com <go...@gmail.com> #15Oct 5, 2024 12:22AM

i had exact issue in s23 ultra as well as on emulator running android 14

Ev...@munice.com <Ev...@munice.com> #16Oct 8, 2024 03:58AM

I have the same issue.
This issues was uploaded on May 21. But why this isn't still fixed?
Google saids GoogleSignInClient is deprecated, and use "powerful" credentialManager.
But there are too many errors I need to handle to use credentialManager.
I need to fix my code to use GoogleSignInClient, until credentialManager get stable.
Please fix this bug faster. I think this issue's priority should go up.

gs...@skroutz.gr <gs...@skroutz.gr> #17Jan 10, 2025 06:38PM

Comment has been deleted.

Message last modified on Jan 13, 2025 09:03AM

eu...@gmail.com <eu...@gmail.com> #18Feb 19, 2025 05:22PM

the same issue on Samsung S24, but we can not reproduce on Pixel 6
any solution guys

eu...@gmail.com <eu...@gmail.com> #19Feb 20, 2025 10:22AM

is it possible to detect current bug and for example switch SignIn flow for user?

eu...@gmail.com <eu...@gmail.com> #20Feb 24, 2025 10:05AM

Hi guys, there's a working solution—use GetSignInWithGoogleOption instead of GetGoogleIdOption. It's unfortunate that the Google Team hasn't suggested this workaround yet. Perhaps even the Google Team is not fully aware of how Credential Manager interacts internally