Currently building an iOS app using Expo CLI / Expo Go and trying to implement Google SSO within using expo-auth-session. I can get to the google sign in page, but every time I try signing in I keep getting a redirect URI error from Google (see below) showing my Expo server IP being used as the redirect URI when it should be getting proxied by expo-auth-session to https://auth.expo.io/@userName/appSlug.
I hit a similar issue, tried google and youtube videos, spent hours, no go. This function worked on 46.0.21, then recently got forced to upgrade to 47 or 48 or 49, chose 49 and hit 2 errors:
Error 1) useAuthRequest() now requires androidClientId, previously expoClientId (Client ID for Web application) alone was fine. My new usage is:
const [request, response, promptAsync] = Google.useAuthRequest({
responseType: ‘token’,
androidClientId: ‘.apps.googleusercontent.com’,
expoClientId: ‘.apps.googleusercontent.com’,
});
But google developer cloud won’t (Invalid Origin: must use either http or https as the scheme) accept URI scheme other than http or https in “Authorized JavaScript origins” and “Authorized redirect URI”.
looks like expo deprecated Google authentication inside expo-auth-session:
Deprecated. See [Google authentication]
on Jul 4: We’ve deprecated Google auth provider from expo-auth-session starting SDK 49. We recommend using a native library such as @react-native-google-signin/google-signin.
Yes running into exactly that pattern @cibym. My issue is I really don’t want to eject from using Expo Go into a custom build, which is required if you want to use @react-native-google-signin/google-signin