byGalax/ChatApp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(mobile): document EAS Secrets contract for EXPO_PUBLIC_*

Browse Source
This commit is contained in:
byGalax
2026-05-16 16:14:23 +02:00
parent affff0b433
commit 3b884b0415
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/mobile/README.md
+17
View File
@@ -73,6 +73,23 @@ Copy `.env.example` to `.env.local` and fill in the same Supabase host +
anon key the desktop uses. Expo bundles only `EXPO_PUBLIC_*`-prefixed
vars into the JS, which is what the three required values use.
## EAS Builds and Environment Variables
Production and preview builds load `EXPO_PUBLIC_*` from EAS Secrets —
`.env.local` is only honoured by `expo start` locally. Without the
secrets configured, an APK installs but `env.ts` throws on first read
and `<BootError>` renders.
Required secrets (create once per project):
```bash
npx eas-cli secret:create --scope project --name EXPO_PUBLIC_SUPABASE_URL --value '<project-supabase-url>'
npx eas-cli secret:create --scope project --name EXPO_PUBLIC_SUPABASE_ANON_KEY --value '<sb_publishable_key>'
npx eas-cli secret:create --scope project --name EXPO_PUBLIC_AUTH_REDIRECT_URL --value 'netralax://auth/callback'
```
Check with `npx eas-cli secret:list`.
## Roadmap
See `docs/superpowers/specs/2026-05-13-mobile-deployment-roadmap.md`.