EAS Update

Publish a bundle exported with your encrypted production configuration.

Complete EAS Update setup and install a build configured for the production channel and a compatible runtime version.

Export with Dotenvx

On a machine with access to the production private key, create a fresh export using the script from the main guide:

$ npm run export

$ pnpm export

This decrypts .env.production before Expo bundles the public variables into dist. EAS variables with Secret visibility cannot be downloaded to your local machine; use your local .env.keys or provision DOTENV_PRIVATE_KEY_PRODUCTION in your CI secret store.

Publish the exported bundle

Use --skip-bundler to publish the export you just created:

$ npx eas-cli@latest update --channel production --environment production --skip-bundler --input-dir dist --message "Update production"

$ pnpm dlx eas-cli@latest update --channel production --environment production --skip-bundler --input-dir dist --message "Update production"

The environment flag selects the EAS environment; it does not replace values already embedded in this exported bundle. Keep the export's app configuration consistent with the installed build.

Re-export before every update after changing configuration. Never publish .env.keys or encrypted .env files as app assets. See the EAS CLI reference for publishing options.