AuthCode is Empty After Successful Sign-In (Post Reinstall or Reconnect)

[Erez-AT]

Hi,

I'm facing an issue on Android where the user signs in with Google successfully, but the returned authCode is empty. This doesn’t happen on the first install — it typically starts occurring after the app is uninstalled and reinstalled, or after reconnecting. It's only get fixed sometimes if going manually to the device Google account settings and disconnect the App from the connected Apps.

I’m fairly confident this used to work properly a couple of months ago — so it might be related to a recent Google Play Services or plugin behavior change.

I'm already call SignOut() before sign-in, which used to solve the problem in the past:

GoogleSignIn.DefaultInstance.SignOut(); // Previously fixed empty authCode
GoogleSignIn.DefaultInstance.SignIn().ContinueWith((Task<GoogleSignInUser> task) => { ... });

Here is my current configuration(If It's helps):

GoogleSignIn.Configuration = new GoogleSignInConfiguration()
{RequestEmail = true,RequestProfile = false,RequestIdToken = false,RequestAuthCode = true, WebClientId = clientID};

Has anyone else experienced this issue recently or found a reliable fix?

Thanks!

[Thaina]

I am not so sure but maybe it related to app cache?

Sometimes uninstalling app did not clear appdata

[Thaina]

Also let's see,

can you set ForceTokenRefresh as true too ?