[Question]: Why Compose Auth plugin native Google One Tap login showing old dialog?

[Premjit-Developer]

General info

• I checked the troubleshooting page for similar problems

What is your question?

This is the Compose Auth plugin googleNativeLogin() implemented version showing old dialog

And this is my own Google One Tap login with Credential-manager implemented version, it is showing the latest One Tap login bottomsheet.

Relevant log output (optional)

No response

[jan-tennert]

Checkout #643

[Premjit-Developer]

It feels awkward to switch from GetGoogleIdOption to GetSignInWithGoogleOption, as it only changes the look without adding much value. I don’t see the need for an additional GetSignInWithGoogleOption when I can create a manual "Login with Google" button and use GetGoogleIdOption, which already works well and has a great BottomSheet UI.

Moreover, GetGoogleIdOption is still recommended in the official snippets. It would be much better if there were an option to let developers choose whether they want to use GetGoogleIdOption or GetSignInWithGoogleOption, providing flexibility for different use cases.

https://developer.android.com/identity/sign-in/credential-manager-siwg#sign-in

[jan-tennert]

Well, the dialog option is recommended for a "Sign in with Google"-Button, the bottom sheet to automatically prompt the user to sign in. And you can disable the bottom sheet option in your Google settings. But I can look into making this configurable.

Add the Sign in with Google button to your app's UI. The Sign in with Google button offers a streamlined way for users to use their existing Google Accounts to sign up or sign in to Android apps. Users will click the Sign in with Google button if they dismiss the bottom sheet UI, or if they explicitly want to use their Google Account for sign up and sign in. For developers, this means easier user onboarding and reduced friction during sign-up.