Environment variables

packages/config/src/env.ts is the only runtime environment access layer. It reads explicit EXPO_PUBLIC_* names, validates them with Zod, caches the result, and exports env plus helper functions.

Every EXPO_PUBLIC_* value is public client configuration. Expo inlines it into the application bundle, where users can inspect it. EAS visibility does not make an EXPO_PUBLIC_* value secret. Never place private API keys, service-account credentials, signing secrets, or server tokens in these variables.

Firebase client keys, OAuth client IDs, RevenueCat public SDK keys, and a OneSignal app ID identify client applications; restrict them in their provider dashboards where supported. Keep privileged operations and secrets on a backend.

Supported variables

Variable	Default	Current use
`EXPO_PUBLIC_API_URL`	`https://api.example.com`	API base URL; must be a valid URL
`EXPO_PUBLIC_APP_ENV`	`development`	Selects `development`, `preview`, or `production` flags and dynamic Expo identity
`EXPO_PUBLIC_FIREBASE_API_KEY`	unset	Firebase app fallback initialization
`EXPO_PUBLIC_FIREBASE_AUTH_DOMAIN`	unset	Optional Firebase app/auth domain
`EXPO_PUBLIC_FIREBASE_PROJECT_ID`	unset	Firebase app fallback initialization
`EXPO_PUBLIC_FIREBASE_STORAGE_BUCKET`	unset	Optional Firebase storage bucket
`EXPO_PUBLIC_FIREBASE_MESSAGING_SENDER_ID`	unset	Firebase app fallback initialization
`EXPO_PUBLIC_FIREBASE_APP_ID`	unset	Firebase app fallback initialization
`EXPO_PUBLIC_FIREBASE_EMAIL_CONTINUE_URL`	unset	Enables in-app email-verification action-code settings
`EXPO_PUBLIC_FIREBASE_AUTH_LINK_DOMAIN`	unset	Optional Firebase dynamic-link domain for verification emails
`EXPO_PUBLIC_GOOGLE_WEB_CLIENT_ID`	unset	Required by the Google sign-in flow
`EXPO_PUBLIC_GOOGLE_IOS_CLIENT_ID`	unset	Optional iOS Google client ID
`EXPO_PUBLIC_REVENUECAT_API_KEY`	unset	Shared RevenueCat public SDK key; takes precedence
`EXPO_PUBLIC_REVENUECAT_IOS_API_KEY`	unset	iOS RevenueCat public SDK key
`EXPO_PUBLIC_REVENUECAT_ANDROID_API_KEY`	unset	Android RevenueCat public SDK key
`EXPO_PUBLIC_ONE_SIGNAL_APP_ID`	unset	Passed to the OneSignal notification adapter
`EXPO_PUBLIC_SENTRY_DSN`	unset	Parsed and exported; not wired into startup currently
`EXPO_PUBLIC_ANALYTICS_ENABLED`	`true`	Parsed by `isAnalyticsEnabled()`; startup currently uses fixed feature flags instead
`EXPO_PUBLIC_DEBUG_MODE`	`false`	Returned by `isDebugMode()`
`EXPO_PUBLIC_DEMO_MODE`	`false`	Forces mock auth, subscriptions, notifications, and analytics

Boolean variables are strings. Only the exact value true becomes true; every other provided string becomes false.

Local development

The repository includes .env.example. Create a gitignored .env.local at the repository root and restart Metro after changes:

cp .env.example .env.local
bun run start:clear

A minimal example is:

.env.local

EXPO_PUBLIC_APP_ENV=development
EXPO_PUBLIC_API_URL=http://localhost:3000
EXPO_PUBLIC_DEMO_MODE=false

EXPO_PUBLIC_GOOGLE_WEB_CLIENT_ID=123456789-example.apps.googleusercontent.com
EXPO_PUBLIC_REVENUECAT_IOS_API_KEY=appl_public_sdk_key
EXPO_PUBLIC_REVENUECAT_ANDROID_API_KEY=goog_public_sdk_key
EXPO_PUBLIC_ONE_SIGNAL_APP_ID=11111111-2222-3333-4444-555555555555

Use an IP address reachable from a physical device instead of localhost when your API runs on your computer.

Manage values in EAS

Run EAS commands from apps/mobile, where eas.json and the linked Expo project live. Create the same variable name separately for each EAS environment:

cd apps/mobile

eas env:set \
  --environment development \
  --name EXPO_PUBLIC_API_URL \
  --value https://dev-api.example.com \
  --visibility plaintext

eas env:set \
  --environment preview \
  --name EXPO_PUBLIC_API_URL \
  --value https://preview-api.example.com \
  --visibility plaintext

eas env:set \
  --environment production \
  --name EXPO_PUBLIC_API_URL \
  --value https://api.example.com \
  --visibility plaintext

Use plaintext or sensitive visibility for values needed while bundling client code. Do not use secret visibility as a security mechanism for EXPO_PUBLIC_* values. List, pull, and delete values with the current EAS environment commands:

# Inspect one environment
eas env:list --environment preview

# Pull one environment into a local .env.local file
eas env:pull --environment development

# Select the value interactively to delete
eas env:delete

The root convenience command bun run env runs the mobile eas env:pull target and moves the generated .env.local to the repository root. The EAS CLI may prompt you to select an environment. Each current build profile sets its EAS environment in apps/mobile/eas.json, so builds receive the matching remote values. Avoid duplicating public values in profile-level env blocks unless you intentionally want values committed to source.

Adapter requirements

Firebase native services: provide the matching native plist/JSON files. The six EXPO_PUBLIC_FIREBASE_* client fields are used only when startup needs to initialize a Firebase app from options; that fallback requires API key, app ID, project ID, and messaging sender ID together.
Firebase email verification: set EXPO_PUBLIC_FIREBASE_EMAIL_CONTINUE_URL; optionally set EXPO_PUBLIC_FIREBASE_AUTH_LINK_DOMAIN.
Google sign-in: set EXPO_PUBLIC_GOOGLE_WEB_CLIENT_ID; optionally set the iOS client ID.
RevenueCat: set the shared key or the key for each target platform. The shared key wins when both forms are present.
OneSignal: set EXPO_PUBLIC_ONE_SIGNAL_APP_ID when notifications.adapter is onesignal.
Mock adapters: require no provider values.

Add a variable

Add every new client variable to both the Zod schema and the explicit raw object in packages/config/src/env.ts. Import it from @amisi-mobile-starter/config; do not read process.env in another package. Update .env.example and every relevant EAS environment.

Configuration

AI

Generators

Packages

Supported variables

Local development

Manage values in EAS

Adapter requirements

Add a variable

Official documentation

Next steps

​Supported variables

​Local development

​Manage values in EAS

​Adapter requirements

​Add a variable

​Official documentation

​Next steps

Supported variables

Local development

Manage values in EAS

Adapter requirements

Add a variable

Official documentation

Next steps