# Mobile env template — copy this to one of:
#   .env.development.local   (used by `*:mobile`         — local backend)
#   .env.staging             (used by `*:mobile:staging`  — remote staging)
#
# All five mobile scripts read one of these two files, depending on suffix:
#   dev:mobile / dev:mobile:staging                    — Metro only
#   ios:mobile:device / ios:mobile:device:staging       — Debug build to iPhone
#   ios:mobile:device:staging:release                   — Release build to iPhone
#
# How EXPO_PUBLIC_* values reach the installed app:
#   - Metro reads this file once at startup and inlines the values into every
#     JS bundle it serves. Editing the file mid-session does NOT auto-refresh
#     — restart Metro (Ctrl+C, then re-run `dev:mobile*`) to pick up changes.
#   - For an installed Release build the value is baked into the embedded
#     bundle at `ios:*:release` time; the only way to change it is to re-run
#     the release build.
#
# Phone must be able to reach this URL. For local dev use your Mac's LAN IP
# (run `ipconfig getifaddr en0`), not `localhost` / `127.0.0.1`.
#
# Staging URL: see apps/desktop/.env.staging (`VITE_API_URL`) for the canonical
# value, or ask a teammate. Same backend across mobile / web / desktop.

EXPO_PUBLIC_API_URL=https://<api-host>

# Optional. Overrides the iOS bundleIdentifier for the DEV variant only so a
# dev whose Apple ID isn't on the Multica Apple Developer team yet can still
# sign local builds. Use a reverse-domain you own (e.g. com.<yourname>.multica).
# Leave unset to use the default ai.multica.mobile.dev.
#
# Only read in `.env.development.local` — staging / production bundle ids are
# never overridable (variants must stay on their canonical ids so the same
# device can hold all three side-by-side).
# EXPO_BUNDLE_IDENTIFIER_DEV=com.yourname.multica.dev