# iOS per-flavor Firebase config — client_app

iOS has **no** automatic per-flavor resolution (unlike Android's
`android/app/src/<flavor>/google-services.json`). Stage the three
`GoogleService-Info.plist` files here, one per flavor:

```
ios/config/
  dev/GoogleService-Info.plist        → bundle com.asc.hallobestie.dev      (dev project)
  staging/GoogleService-Info.plist    → bundle com.asc.hallobestie.staging  (staging/nonprod)
  prod/GoogleService-Info.plist       → bundle com.asc.hallobestie          (prod project, live App Store app)
```

> The customer iOS bundle base is **`com.asc.hallobestie`** (the existing App
> Store app), NOT the Android `com.mybestie`. See `../../BUILD_FLAVORS.md`.

## Wiring (Xcode — Mac follow-up, not done yet)

The active plist Xcode bundles is `ios/Runner/GoogleService-Info.plist`. To make
it per-flavor, add a **Run Script** build phase to the Runner target, placed
**before** "Compile Sources":

```bash
cp "${PROJECT_DIR}/config/${FLAVOR}/GoogleService-Info.plist" \
   "${PROJECT_DIR}/Runner/GoogleService-Info.plist"
```

`${FLAVOR}` is a per-scheme/configuration build setting you define when creating
the dev/staging/prod schemes (e.g. `FLAVOR = dev` in the dev configuration).

### Single-env shortcut
If you only need one env working (e.g. dev) before the full scheme setup, just
drop that env's plist directly at `ios/Runner/GoogleService-Info.plist` — no
script needed for a single environment.