expo: After upgrading the expo-auth-session to 4, an error occurs when calling authUrl with startAsync.

I have run into a similar issue but using google login in Expo Go:

ValidationError: “redirect uri” is not allowed. “client id” is not allowed. “response type” is not allowed. “state” is not allowed. “scope” is not allowed

I got this error in the console: WARN The useProxy option is deprecated and will be removed in a future release, for more information check https://expo.fyi/auth-proxy-migration.

But we do not call useProxy in our code.

const [googleRequest, googleResponse, googlePromptAsync] =
    Google.useIdTokenAuthRequest({
      expoClientId: webClientId,
      iosClientId: iosClientId,
      androidClientId:
        (Constants.appOwnership !== 'expo' && androidClientId) || webClientId,
      redirectUri: makeRedirectUri({
        scheme: config.native.scheme,
      }),
    })

I have tried both with and without redirectUri specified.

“expo-auth-session”: “^4.0.3”, expo 48.0.4

This worked fine with expo 47

Ive read it and don’t think it helps. It says that it’s deprecated in 48, not that the functionality is removed.

Also removing support for logging in using Google in expo go is quite a big loss of functionality. It would be great if expo could reconsider this decision.

exact same issue for me, ValidationError: “redirect uri” is not allowed. “client id” is not allowed. “response type” is not allowed. “state” is not allowed. “scope” is not allowed

It appears that this issue is limited to iOS devices. I have tested it on Expo 47 and 48 and noticed the only difference is in the URL. Here are the URLs I copied from Safari:

Expo 47 (working): https://auth.expo.io/@xxxx/xxxx/start?authUrl=https%3A%2F%2Fxxxx.supabase.co%2Fauth%2Fv1%2Fauthorize%3Fprovider%3Dgoogle%26redirect_to%3Dexp%3A%2F%2F192.168.0.106%3A19000%2F--%2Fauth%2Fcallback&returnUrl=exp%3A%2F%2F192.168.0.106%3A19000%2F--%2Fauth%2Fcallback

Expo 48 (not working): https://auth.expo.io/@xxxx/xxxx/start?authUrl=https://xxxx.supabase.co/auth/v1/authorize?provider=google&redirect_to=exp://192.168.0.106:19000/--/auth/callback&returnUrl=exp://192.168.0.106:19000/--/auth/callback

When opening these links on Windows, I noticed different payload requests, as shown in this image:

So far, I have not found a working workaround. It seems that the issue is related to the encoding being removed and the browser taking the authUrl parameters for the auth.expo.io URL instead.

Same issue, any advice is appreciated

I have run into a similar issue but using google login in Expo Go:

ValidationError: “redirect uri” is not allowed. “client id” is not allowed. “response type” is not allowed. “state” is not allowed. “scope” is not allowed

I got this error in the console: WARN The useProxy option is deprecated and will be removed in a future release, for more information check https://expo.fyi/auth-proxy-migration.

But we do not call useProxy in our code.

const [googleRequest, googleResponse, googlePromptAsync] =
    Google.useIdTokenAuthRequest({
      expoClientId: webClientId,
      iosClientId: iosClientId,
      androidClientId:
        (Constants.appOwnership !== 'expo' && androidClientId) || webClientId,
      redirectUri: makeRedirectUri({
        scheme: config.native.scheme,
      }),
    })

I have tried both with and without redirectUri specified.

“expo-auth-session”: “^4.0.3”, expo 48.0.4

This worked fine with expo 47

I have the same issue. Has anyone found a solution?

Thank you for filing this issue! This comment acknowledges we believe this may be a bug and there’s enough information to investigate it. However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

It is happening to everyone. For the good of the repo mantainers try not commenting “me too” that isn’t helpful at all for the team and other members. That said I solved the same issue migrating to an AuthRequest object and it works exactly the same. Here is an example:

const redirect = AuthSession.makeRedirectUri({ path: 'sign-in' })

const request = new AuthSession.AuthRequest({
  clientId: Constants?.manifest?.extra?.yourPlatformId
  redirectUri: redirect,
  prompt: AuthSession.Prompt.SelectAccount
})

const result = await request.promptAsync({
  authorizationEndpoint: authenticationURL
})

const code = JSON.parse(JSON.stringify(result)).params.code

I had the same problem. It appears that a change was made in Expo Go where Google Login does not work.

https://github.com/expo/fyi/blob/main/auth-proxy-migration.md

Well I just followed the article and created a development build on Android and it seems to work fine.

https://github.com/expo/fyi/blob/main/auth-proxy-migration.md