expo: ValidationError: "returnUrl" must be a valid uri

same here… don’t know how to solve it

we deprecated the auth proxy (useProxy), which is what AuthSession.startAsync is meant for. I recommend using useAuthRequest if you’re interacting with an openid/oauth service, or otherwise, use WebBrowser.openAuthSessionAsync() instead, which has nothing to do with the deprecated auth proxy.

we’re working on cleaning this all up for sdk 49

I spoke too soon. The solutions above work for starting the login flow but Android fails to return back to the app after login. I dug a little further and it seems that the actual issue resides in the Linking.isExpoHost() function. On SDK 44, this function returns true for us under Expo Go but on SDK 45 it returns false. This seems to be related to moving Constants.manifest in SDK 44. Below is an updated patch we use with patch-package that works for us.

diff --git a/node_modules/expo-linking/build/Linking.js b/node_modules/expo-linking/build/Linking.js
index 6915cf7..be224e2 100644
--- a/node_modules/expo-linking/build/Linking.js
+++ b/node_modules/expo-linking/build/Linking.js
@@ -29,8 +29,12 @@ function getHostUri() {
 function isExpoHosted() {
     const hostUri = getHostUri();
     return !!(hostUri &&
-        (/^(.*\.)?(expo\.io|exp\.host|exp\.direct|expo\.test)(:.*)?(\/.*)?$/.test(hostUri) ||
-            Constants.manifest?.developer));
+        (
+            /^(.*\.)?(expo\.io|exp\.host|exp\.direct|expo\.test)(:.*)?(\/.*)?$/.test(hostUri) ||
+            Constants.manifest?.developer ||
+            Constants.manifest2?.extra?.expoGo?.developer
+        )
+    );
 }
 function removeScheme(url) {
     return url.replace(/^[a-zA-Z0-9+.-]+:\/\//, '');
diff --git a/node_modules/expo-linking/src/Linking.ts b/node_modules/expo-linking/src/Linking.ts
index 56823aa..78dbbe2 100644
--- a/node_modules/expo-linking/src/Linking.ts
+++ b/node_modules/expo-linking/src/Linking.ts
@@ -37,10 +37,19 @@ function getHostUri(): string | null {
 
 function isExpoHosted(): boolean {
   const hostUri = getHostUri();
-  return !!(
-    hostUri &&
-    (/^(.*\.)?(expo\.io|exp\.host|exp\.direct|expo\.test)(:.*)?(\/.*)?$/.test(hostUri) ||
-      Constants.manifest?.developer)
+  return !!(hostUri &&
+      (
+          /^(.*\.)?(expo\.io|exp\.host|exp\.direct|expo\.test)(:.*)?(\/.*)?$/.test(hostUri) ||
+          Constants.manifest?.developer ||
+          // `Constants.manifest?.developer` is no longer set under Expo 45 and
+          // seems to have moved under `manifest2.extra.expoGo`.
+          // See https://github.com/expo/expo/issues/18130
+          //
+          // Remove this patch when:
+          // ----------------------
+          // Login with Expo Go works without it.
+          Constants.manifest2?.extra?.expoGo?.developer
+      )
   );
 }

However, there’s a good chance that our upgrade path left us with some incorrect config somewhere. Here’s our app.json:

{
  "expo": {
    "owner": "apartment-snapshot",
    "name": "Apt Snap",
    "slug": "snapshot-ui",
    "version": "3.2.2",
    "orientation": "portrait",
    "icon": "./assets/icon-inverse.png",
    "scheme": "ourschemehere",
    "currentFullName": "...",
    "originalFullName": "...",
    "splash": {
      "image": "./assets/splash.png",
      "resizeMode": "cover",
      "backgroundColor": "#F44C7F"
    },
    "runtimeVersion": {
      "policy": "sdkVersion"
    },
    "updates": {
      "fallbackToCacheTimeout": 0,
      "url": "https://u.expo.dev/..."
    },
    "assetBundlePatterns": [
      "**/*"
    ],
    "ios": {
      "bundleIdentifier": ...,
      "buildNumber": "3.2.2",
      "supportsTablet": true,
      "config": {
        "usesNonExemptEncryption": false
      }
    },
    "android": {
      "package": ...,
      "versionCode": 440030202,
      "adaptiveIcon": {
        "foregroundImage": "./assets/icon-inverse.png",
        "backgroundColor": "#FFFFFF"
      }
    },
    "web": {
      "favicon": "./assets/favicon.png"
    },
    "extra": {
      "eas": {
        "projectId": ...
      }
    }
  }
}