Configure environment variables for the mobile app. Use when setting up .env files, API keys, or environment-specific configuration. Invoked by: "env", "environment variables", ".env", "configuration", "api keys".
Version: 1.0.0 Last Updated: 2026-01-11 Status: Active
Note: This is a template. Replace placeholders like
{PROJECT_NAME},{BUNDLE_ID},{APP_SLUG}, and{BASE_URL}with your actual project values.
This SOP guides developers through configuring environment variables for the mobile app. Proper environment configuration is essential for connecting to APIs, enabling features, and managing different deployment environments.
ALWAYS: Initial project setup, switching between dev/prod environments, configuring API keys, setting up Firebase credentials : Only running tests (defaults work), making code changes that don't affect configuration
[Quick Setup] --> [Configure Variables] --> [Firebase Credentials] --> [Verify]
| Phase | Objective | Deliverable |
|---|---|---|
| 1. Quick Setup | Create .env from template | .env file exists |
| 2. Configure | Set required variables | Variables populated |
| 3. Firebase | Configure push notifications | Credential files in place |
| 4. Verify | Confirm configuration works | task env-check passes |
# Development environment
task setup-dev
# Runs: ./scripts/pull-expo-env.sh development
# Production environment
task setup-prod
# Runs: ./scripts/pull-expo-env.sh production
Note: Requires EAS CLI login:
npx eas login
# Copy template to .env
cp .env.example .env
# Edit with your values
nano .env
| File | Purpose | Git Status |
|---|---|---|
.env.example | Template with defaults | Committed |
.env | Actual values | Gitignored |
The Taskfile.yml loads environment files in order: