# Shared variables for all client_app Maestro flows.
#
# Override at runtime with `maestro test --env KEY=value` or by setting shell env vars.
# See README.md for full setup + per-machine overrides.

env:
  # App identifiers — Android / iOS bundle IDs picked up automatically by `appId:` in flows.
  APP_ID_ANDROID: com.halobestie.client.client_app
  APP_ID_IOS: com.halobestie.client.clientApp

  # Backend the app talks to — must match what the installed APK was built with
  # (the `--dart-define=API_BASE_URL=...` value at build time).
  BACKEND_URL: http://192.168.88.247:3000
  BACKEND_INTERNAL_URL: http://192.168.88.247:3001

  # Test customer credentials — must exist in the customers table on the target backend.
  # These are read by helper scripts (see .maestro/scripts/) when seeding state.
  CUSTOMER_PHONE: "+628100000001"
  CUSTOMER_OTP: "123456"   # OTP stub mode emits a known code per phone

  # If you need to drive a "second actor" (e.g., the mitra accepting a blast), the test
  # flows curl the backend directly using these credentials. See README §"Single-emulator
  # + curl pattern" for details.
  TEST_MITRA_ID: "REPLACE-WITH-A-REAL-MITRA-UUID"
  TEST_MITRA_JWT: "REPLACE-WITH-A-VALID-MITRA-JWT"