Auth session sometimes ends with "Something went wrong trying to finish signing in."
Problem
Maintainer edit The auth session proxy service is deprecated and not recommended for production. For production apps, your app should navigate to the third-party authentication provider directly instead of using this service. This is the official workaround to this issue, which is likely unresolvable due to how browser cookie policies have changed. Follow this migration guide if you are currently using the proxy service. The migration guide shows how to configure the authentication provider to redirect directly to your app, typically with a deep link with your app's own URL scheme. In your app, set the useProxy option to false (the default) when calling the promptAsync method, which configures your app not to use this service. Due to web browser changes like WebKit's Tracking Prevention, the AuthSession proxy service may not work reliably in edge cases such as when a user's device is configured to block cookies or prevent cross-site tracking. The AuthSession proxy service does not track nor collect any user data but it requires cookies to correctly redirect back to your app after the user has authenticated with the third-party authentication provider. This service will not work if the browser's settings or heuristics block cookies. --- ๐ Bug Report Summary of Issue (just a few sentences) Sometimes when I try logging in using AuthSession it doesn't redirect me back to app, but shows "Something went wrong trying to finish signing in." instead. After that when I try agai
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Auth session sometimes ends with "Something went wrong trying to finish signing in."
For future reference, I hit this error today when I misused the proxy. [code block] This caused the auth to open up to the provider (e.g. facebook.com) but redirect to the proxy `auth.expo.io` when it was complete. The error was the result of the auth proxy not being able to complete the result because I forgot to start it.
Trust Score
3 verifications
- 1
For future reference, I hit this error today when I misused the proxy.
For future reference, I hit this error today when I misused the proxy.
- 2
This caused the auth to open up to the provider (e.g. facebook.com) but redirect
This caused the auth to open up to the provider (e.g. facebook.com) but redirect to the proxy `auth.expo.io` when it was complete. The error was the result of the auth proxy not being able to complete the result because I forgot to start it.
Validation
Resolved in expo/expo GitHub issue #8957. Community reactions: 4 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep