signInWithOAuth for React Native without @react-native-google-signin/google-signin

I have been using my implementation for almost 2 years:

 supabase.auth.signInWithOAuth({
      provider: 'google',
      options: {
        redirectTo: 'myMobileSchema://',
      },
    });

 supabase.auth.signInWithOAuth({
      provider: 'google',
      options: {
        redirectTo: 'myMobileSchema://',
      },
    });

Now today, none of it works in dev or prod!?! after opening the oAuth consent, it just redirects to my website URL, not back to my mobile app.

1. Can signInWithOAuth be used in React Native without the "native" GoogleSigninButton. I hate that library
2. If so, can I share the same web based Client secret & Client ID in the Supabase sign in provider? I did ensure the web based client id is first.

Did something change? This is not ideal to have break out of the blue.

What's super interested is that according to google my "iOS" Client Ids have warnings:

This OAuth client has not been used. Inactive OAuth clients are subject to deletion if they are not used for 6 months. Learn more

This makes me thing something else is going on...

Supabase•4mo ago•

56 replies

lucksp

signInWithOAuth for React Native without @react-native-google-signin/google-signin

I have been using my implementation for almost 2 years:

 supabase.auth.signInWithOAuth({
      provider: 'google',
      options: {
        redirectTo: 'myMobileSchema://',
      },
    });

 supabase.auth.signInWithOAuth({
      provider: 'google',
      options: {
        redirectTo: 'myMobileSchema://',
      },
    });

This OAuth client has not been used. Inactive OAuth clients are subject to deletion if they are not used for 6 months. Learn more

This makes me thing something else is going on...

signInWithOAuth for React Native without @react-native-google-signin/google-signin

Similar Threads

signInWithOAuth for React Native without @react-native-google-signin/google-signin

Similar Threads

Similar Threads

Similar Threads