Back to threads
Loading user profile...
A user expressed concern about scheduled maintenance occurring during the middle of the day, suggesting it should be done at night when there is less activity. Another user clarified that the maintenance spans a week and can occur at any time, advising that this forum is not the right place for such requests.
The user is experiencing an issue where the `signInWithOAuth` function in a React Native app does not trigger the expected Google Auth Client activity. They suspect the problem might be related to using a web client with deep linking instead of a native setup. The user also notes warnings from Google about inactive OAuth clients, questioning the accuracy of the documentation regarding mobile app setup.
yes, I am using server actions or calling supabase directly from my server components
thanks all for the quick jump on this!
None
this is not a duplicate - i happened to notice this as I began debugging before I sent in the the report with Supa in the other thread.
same guy - different questions...
yes
it's working! 🎉
nothing obviously deployed yet - still an issue AFAIK
Have you gone to a functional medicine person ? they can run actual tests also
I’ll be happy to test it as reported the issue
Ok. I have an appointment now so I’ll check in after
Is instance ID the same as project ID? What is the ticket I can follow along to?
I don’t think mine counts as deeplink but here’s my snippet that I’ve used for well over a year which just stopped today : const signInWithGoogle = async () => { const { data, error } = await supabase.auth.signInWithOAuth({ provider: 'google', options: { redirectTo: 'myflyid://', }, }); if (error) { setMessage(['error', error.message]); return; } if (data.url) { const result = await openAuthSessionAsync(data.url, 'myflyid://'); if (result.type === 'success') { const params = extractTokensFromUrl(result.url); if (!params.access_token || !params.refresh_token) return; setOAuthSession({ access_token: params.access_token, refresh_token: params.refresh_token, }); } } }; const setOAuthSession = async (tokens: { access_token: string; refresh_token: string; }) => { const { data, error } = await supabase.auth.setSession({ access_token: tokens.access_token, refresh_token: tokens.refresh_token, }); if (error) { __DEV__ ? console.error(error) : Bugsnag.notify({ name: 'Auth setOAuthSession Error', message: (error as Error).message, }); return; } setSession(data.session); };
As we’re waiting to find out if there is an issue on supabases side, or not, is the flow of using signinwithOAuth valid with react native, since it’s not technically a Web app?
"supabase": "^2.26.9", "react-native": "0.79.6", "@supabase/supabase-js": "^2.78.0",
basically, just checking if there's a token stored on device, and granting them access....when offline