@@ -232,6 +232,47 @@ pnpm install
232232
233233If you already have the repo locally, running ` pnpm install` at the root is enough.
234234
235+ # # Google Maps API Key Setup (Local + CI)
236+
237+ Android uses ` react-native-maps` , so a Google Maps Android API key is required.
238+ This repo now reads the key from ` GOOGLE_MAPS_ANDROID_API_KEY` at build/config time.
239+
240+ # ## Local development
241+
242+ 1. Copy the example env file:
243+ ` ` ` bash
244+ cp apps/mobile/.env.example apps/mobile/.env.local
245+ ` ` `
246+ On Windows PowerShell:
247+ ` ` ` powershell
248+ Copy-Item apps/mobile/.env.example apps/mobile/.env.local
249+ ` ` `
250+ 2. Edit ` apps/mobile/.env.local` and set:
251+ ` ` ` env
252+ GOOGLE_MAPS_ANDROID_API_KEY=your_real_android_maps_key
253+ ` ` `
254+ 3. Rebuild the Android app after changing the key:
255+ ` ` ` bash
256+ pnpm -C apps/mobile android
257+ ` ` `
258+
259+ # ## GitHub Actions (EAS build workflow)
260+
261+ 1. In GitHub, add repository secret:
262+ - Name: ` GOOGLE_MAPS_ANDROID_API_KEY`
263+ - Value: your Android Maps key
264+ 2. The workflow ` .github/workflows/eas-build.yml` injects this secret into the build job.
265+ 3. Android/all builds fail early with a clear message if the secret is missing.
266+
267+ # ## Security recommendations
268+
269+ - Restrict the key in Google Cloud Console to:
270+ - Application restriction: ` Android apps`
271+ - Package: ` com.lallimaven.eclipsetimer`
272+ - SHA-1: your debug/release certificate fingerprints
273+ - Restrict API usage to ` Maps SDK for Android` .
274+ - If a key was ever committed, rotate it in Google Cloud and replace it in local/CI secrets.
275+
235276# # Getting Started (Quick Start)
236277
237278From the repo root:
0 commit comments