Managing secrets for development and production builds [EAS]

Expo Application Services (EAS)
1

Hi,

What is the best practice for managing secrets for development and production builds. There may be secrets, such as access tokens or app identifiers, that need to be kept secret, but have different values on development and production environments. AFAIK, there’s no way to have two separate sets of secrets for development and production builds on Expo website, and eas.json is meant to be public. For example, environment variable TOKEN=“abc” on dev and TOKEN=“xyz” on prod. How to proceed?

In your post, please share:

  • Whether you are bare or managed workflow: MANAGED
  • Your eas-cli version: 2.2.1
  • What you have tried so far: Read the documentation on environment variables and secrets.