EAS Build: Can't use dynamic app name about eas-cli HOT 2 OPEN

Hey,

I suspect that you get this error because when resolving credentials for your project you don't have APP_NAME env var set locally when running eas build and we use the fallback value from package.json. Secrets are only available during cloud builds and are not accessible in EAS CLI when resolving stuff.

What I think you can do is add APP_NAME to the env section of your eas.json. I don't think that app name is a secret, is it? I would also remove it from secrets.

{
  "build": {
    "production": {
      "env": {
        "APP_NAME": "myappname"
      }
    }
  }
}

from eas-cli.

@szdziedzic Thanks for the response. I'm on the same page with you.
But there are two questions then:

1. If I'm developing a multi-tenat app (same codebase, multiple Expo projects and apps in AppStore/PlayStore) - I have to store two unique identifiers (project id and project slug) for each project outside of Expo. And now it turned out that I also need to store app name for each project. I'm curious why having just project id isn't enough (for submitting a build).
2. I'm also curious why it doesn't work the same way for app identifiers then? Even if I don't have ios.bundleIdentifier and android.package and provide fallback (see the screenshot) - I'm able to submit a build and an identifier will be taken from the EAS Secrets and used for my build.

from eas-cli.