Helped me through, despite not being the same problem the use the URL quote helped me solve this by changing a bit how I thought about it!
The final result became a little too big to paste here, but the handling ended up being relatively straightforward:
useEffect(() => { if (result?.type === "success") { const { token, iv } = getParamsFromUrl(result.url) const session = decrypt(token, key, iv) console.log({ session }) } }, [result])
Videos
Update: found the issue. It was caused by the discovery failing silently. The example code is not well engineered here. There should be a check (even in the example) that detects errors when doing the discovery part.
If you are encountering this, make sure the actual endpoint URL delivered to the auth mechanism is actually set from the discovery.
In My case it was like missing scheme. After adding it worked in expo go
{
"expo": {
"scheme": "your-app-slug"
}
}
Is there any way to authenticate through Google using webview or expo-web-browser?
Because I don't want to touch the native files (ios - android)
» npm install expo-auth-session
Try this:
-Login to your expo account: on command line type:
expo login
##then your account credencials##
then restart your expo instance:
expo start
And everything should work fine
I have the exact same issue. I've posted on the Expo forums too and tried to contact the devs about it but nobody's responding to me. I think it's been broken with a recent change. If you look at the redirect URL it's supposed to have two more query parameters one for the authentication URL and one for the return URL