IssueTracker

Component used: Credentials

Version used: 1.2.2 (also reproduced on 1.3.0-rc01 and 1.5.0-alpha05)

targetSdk = 34

androidx.credentials:credentials:1.2.2

androidx.credentials:credentials-play-services-auth:1.2.2

com.google.gms.google-services:4.4.2

We use Proguard, but we have added the rules, as indicated inside your documentation, and it is compiling on release build.

Devices/Android versions reproduced on: Redmi Note 10 Pro/Android 12, Galaxy S20 FE/Android 13

We tried to migrate from com.google.android.gms:play-services-auth: 20.7.0 to androidx.credentials:credentials:1.2.2. With that new library we are using the functionality to create credentials after a successful login :

credentialManager?.createCredential(
context = it,
request = CreatePasswordRequest(email, password)
 )

On Redmi Note 10 Pro/Android 12: on our Release application version, we still observe an old bottomsheet (see old_bottomsheet.png attachment), which appeared only if the credentials doesn’t exist inside the google account or if the password has changed. That was the comportment we were looking for.

On Galaxy S20 FE/Android 13: on our Release and debug application version (and on Redmi Note 10 Pro/Android 12 on our debug version), we observe a different bottomsheet (see new_bottomsheet.png), which appeared after every login, even if the credentials have already been saved inside google account. We didn’t change the code between the tests.

Is there any way not to display the bottomsheet if the credentials already exist, without checking for noCredentialException? Our users are able to change their password inside and outside the application (from website for example), and should be able to save the new credentials inside their google account on a new login.

Thank you