Assigned
Status Update
Comments
ch...@gmail.com <ch...@gmail.com> #2
Automated by Blunderbuss job android-credential-manager-autoassigner for config android_credman_config for component 1301097.
bl...@google.com <bl...@google.com> #3
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?
da...@google.com <da...@google.com> #4
Hmm from the description, it's hard to tell whether the users failing to sign in are intended because there are no available credentials or it's a bug. Is there a way to reproduce the issue, or grab bugreports when it happens so we can take a look?
ch...@gmail.com <ch...@gmail.com> #5
At present, our developers cannot reproduce this problem. Can you give some solutions based on the error? So that online users can log in normally.
In addition, if there is no available credentials for Google button login, I understand that the Google account login panel should be pulled up instead of blocking the login process.
As for error reports, we will try to find users to help report them. I will tell you in the comments after reporting.
In addition, if there is no available credentials for Google button login, I understand that the Google account login panel should be pulled up instead of blocking the login process.
As for error reports, we will try to find users to help report them. I will tell you in the comments after reporting.
Description
There are two types of error messages:
1. During get sign-in intent, failure response from one tap: 16: [28434] Cannot find an eligible account.
2. No credentials available
Originally, the Google button was used to log in to GoogleSignInOptions. After the update, GetSignInWithGoogleOption was used:
GetSignInWithGoogleOption mOption = new GetSignInWithGoogleOption.Builder("myGoogleWeb
GetCredentialRequest credentialRequest = new GetCredentialRequest.Builder()
.addCredentialOption(mOption)
.build();ClientId").build();
There was no problem when we tested it, but after the app was launched, many users reported errors and could not log in. I hope you can help me find a solution as soon as possible.