Manifest missing originalFullName in EAS Build Development Client

Summary

Manifest is missing originalFullName and currentFullName (and id) when using custom EAS Build Development client.

Managed or bare workflow? If you have made manual changes inside of the ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android, iOS

Package versions

Only native and expo packages listed:

{
  "dependencies": {
    "expo": "^42.0.0",
    "expo-application": "~3.2.0",
    "expo-asset": "~8.3.2",
    "expo-auth-session": "~3.3.1",
    "expo-camera": "~11.2.1",
    "expo-constants": "~11.0.1",
    "expo-dev-client": "^0.4.3",
    "expo-device": "~3.3.0",
    "expo-image-picker": "~10.2.2",
    "expo-linear-gradient": "~9.2.0",
    "expo-linking": "~2.3.1",
    "expo-localization": "~10.2.0",
    "expo-notifications": "~0.12.2",
    "expo-random": "~11.2.0",
    "expo-secure-store": "~10.2.0",
    "expo-splash-screen": "~0.11.2",
    "expo-standard-web-crypto": "^1.0.2",
    "expo-status-bar": "~1.0.4",
    "expo-updates": "~0.8.0",
    "react": "16.13.1",
    "react-dom": "16.13.1",
    "react-native": "https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz",
    "react-native-gesture-handler": "~1.10.2",
    "react-native-reanimated": "~2.2.0",
    "react-native-safe-area-context": "3.2.0",
    "react-native-screens": "~3.4.0",
    "react-native-svg": "12.1.1",
    "sentry-expo": "^4.0.0",
  }
}

Environment

Expo CLI 4.7.2 environment info:
    System:
      OS: Windows 10 10.0.19042
    Binaries:
      Node: 12.18.2 - ~\AppData\Local\Temp\yarn--1625626459530-0.2547605146813341\node.CMD
      Yarn: 1.22.10 - ~\AppData\Local\Temp\yarn--1625626459530-0.2547605146813341\yarn.CMD
      npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
    npmPackages:
      expo: ^42.0.0 => 42.0.0
      react: 16.13.1 => 16.13.1
      react-dom: 16.13.1 => 16.13.1
      react-native: https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz => 0.63.2
      react-native-web: ~0.13.12 => 0.13.18
    Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

1. Create new expo 42 project
2. Create a development client:

{
  "builds": {
    "android": {
      "debug": {
        "workflow": "managed",
        "buildType": "development-client",
        "releaseChannel": "test.42.0",
        "distribution": "internal"
      }
    }
  }
}

1. Try to create a redirect URI:

const useProxy = Platform.select({ web: false, default: true });
const redirectUri = AuthSession.makeRedirectUri({ useProxy });

1. Start expo start --dev-client
2. Install the dev client and connect
3. It breaks

I went into node_modules\expo-auth-session\build\SessionUrlProvider.js and added console.log({ manifest }). I can see in the log that both originalFullName and currentFullName are missing.

expo config --type public

This correctly shows originalFullName and currentFullName.

Workaround

import Constants from 'expo-constants';
Constants.manifest.originalFullName = '@org/project';

Right before AuthSession.makeRedirectUri

Stacktrace (if a crash is involved)

SessionUrlProvider.js

Error: Cannot use AuthSession proxy because the project ID is not defined. Please ensure you have the latest version of expo-constants installed and rebuild your native app. You can verify that currentFullName is defined by running expo config --type public and inspecting the output.

[SleeplessByte]

It’s not resolved.

[soullivaneuh]

It seems you’re using eas anyway.

Yes but I do have this issue using eas! By the way, I’m not trying to use the same variables as you, I try to fetch a extra.apiEndpoint custom var we defined.

My https://github.com/expo/expo/issues/13513#issuecomment-1237238178 works with that without any hardcoding. I’m using that solution in production too 😃

Indeed, you don’t have value hardcoded on your code. However, what a complex custom logic just for a not provided manifest property. 😕

I think I’ll just be careful of doing a eas upate command just after the eas build to be sure the app load the configuration correctly until I do the upgrade to SDK 46.

Thanks for the help! 👍