- Customer: com.halobestie.client.client_app → com.mybestie - Mitra: com.halobestie.mitra.mitra_app → com.mybestie.mitra - iOS bundle IDs renamed to match (no .clientApp/.mitra camelCase legacy) Mechanical rename touches Android build.gradle/Manifest/MainActivity package, iOS pbxproj/Info.plist bundle IDs, Firebase configs (google-services.json + GoogleService-Info.plist + firebase_options.dart), new HaloBestie/Mitra launcher icons via flutter_launcher_icons (pubspec config + adaptive-icon resources + AppIcon imageset), and the appId references in every customer maestro flow + both .maestro/config.yaml files. brandLogoBg (#FF699F) added to halo_tokens for the launcher pink. Followup: re-register apps in Firebase consoles using the new package IDs; strategy memo at project-firebase-env-strategy. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
23 lines
873 B
YAML
23 lines
873 B
YAML
# Shared variables for all mitra_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
|
|
APP_ID_ANDROID: com.mybestie.mitra
|
|
APP_ID_IOS: com.mybestie.mitra
|
|
|
|
# Backend the app talks to — must match what the installed APK was built with.
|
|
BACKEND_URL: http://192.168.88.247:3000
|
|
BACKEND_INTERNAL_URL: http://192.168.88.247:3001
|
|
|
|
# Test mitra credentials — must exist in the mitras table on the target backend.
|
|
MITRA_PHONE: "+628200000001"
|
|
MITRA_OTP: "123456"
|
|
|
|
# If you need to drive a "second actor" (e.g., a customer creating a blast), the test
|
|
# flows curl the backend directly using these credentials.
|
|
TEST_CUSTOMER_ID: "REPLACE-WITH-A-REAL-CUSTOMER-UUID"
|
|
TEST_CUSTOMER_JWT: "REPLACE-WITH-A-VALID-CUSTOMER-JWT"
|