Questions

We have the Social Login plugin set up as described in the documentation and that's been working fine for our current release. The problem only seems to occur for a new Android build (a new build for iOS still seems to work fine).

Looking at the Appetize debug logs, whenever our "Login with Google" button is pressed, it shows the following error:

I/CredManProvService( 6918): GetCredentialResponse error returned from framework
E/a ( 6918): signIn:
E/a ( 6918): u0.p: No credentials available
E/a ( 6918): at t0.M.c(SourceFile:33)
E/a ( 6918): at t0.M$e.a(SourceFile:17)
E/a ( 6918): at t0.M$e.onError(SourceFile:5)
E/a ( 6918): at android.credentials.CredentialManager$GetCredentialTransport.lambda$onError$2(CredentialManager.java:694)
E/a ( 6918): at android.credentials.CredentialManager$GetCredentialTransport.$r8$lambda$nlbYav9mLBoE6Yh1vFKCvITF3ks(Unknown Source:0)
E/a ( 6918): at android.credentials.CredentialManager$GetCredentialTransport$$ExternalSyntheticLambda2.run(Unknown Source:6)
E/a ( 6918): at t0.i.execute(SourceFile:1)
E/a ( 6918): at android.credentials.CredentialManager$GetCredentialTransport.onError(CredentialManager.java:693)
E/a ( 6918): at android.credentials.IGetCredentialCallback$Stub.onTransact(IGetCredentialCallback.java:123)
E/a ( 6918): at android.os.Binder.execTransactInternal(Binder.java:1344)
E/a ( 6918): at android.os.Binder.execTransact(Binder.java:1275)

Reading the Android release notes, that states:

May 15 - Maintenance 🛠️
Google Sign-In now uses the new CredentialsManager API for faster and more secure login on Android

It seems, a different method for Google Login is now used. I assume that the problem is related to that. Is this a bug or do we need to set something else up for the CredentialManager API to properly function? If so, there doesn't seem to be any mention of it in the documentation.

Any help would be appreciated.