Request for the Google Sign up flow for new user

[chiragbachwani]

Steps to reproduce

I am not able to understand how Google Sign-In should work for a new user. Right now, I am using the oAuthTokenGoogle strategy, and in the attemptSignIn method we have a field to pass the token received from the Google Sign-In package.

But for a completely new user, the sign-in method detects an external account error and does not allow the new user to create an account. So then I try to use the attemptSignUp function as a fallback , but this function does not have a field to pass the token received from Google Sign-In.

How can I achieve this functionality for new users?
I do not want to use the SSO Sign-In because for the Google strategy it takes the user to a web page and asks them to log into their Google account again, which is not a good user experience. So I want to continue using the Google One-Tap (oAuthTokenGoogle) strategy.

Please guide me on the correct flow for this.

Expected results

The user (No matter new or old) should be able to just use a single function to create and login or simple log in to the account.

Actual results

The new user cannot use the oauthtoken google stratergy to create an account

Code sample

Code sample

[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

Logs

[Paste your logs here]

Flutter Doctor output

Doctor output

[Paste your output here]

[shinyford]

Hi @chiragbachwani - apologies for taking so long to get back to you here.

Can you tell me if this issue is still a problem for you, with the latest versions of the API?

Many thanks

Nic

[briardg]

Hello,

I have also something that look to be the same, basically on IOS or Android SSO Signin for new user so basically sign-up is never working.

clerk_auth 0.0.13-beta
├── clerk_flutter 0.0.13-beta

[shinyford]

Are you talking about when you sign in via Google SSO (for example) and create a new account rather than use an existing account? @briardg @chiragbachwani

[chiragbachwani]

Yes , @shinyford i am talking about this. Also do we have a status for the documentation of the clerk sdk flutter so that these type of things can be found there?

[shinyford]

Okay, I think I've spotted what's causing this. I'll pick it up.

Documentation is currently as you find it from the code and comments within. We are of course intending to improve this before taking the SDK out of beta; but at the moment we're concentrating on getting the wrinkles ironed out.

[chiragbachwani]

okay thanks! looking forward to this