chore(mobile): dynamic store config for demo credentials and version
Merged
SA
3mo ago+48+48+01234567890123456789-40-40-01234567890123456789
First eas metadata:push surfaced two ASC requirements: demoRequired: true must ship demoUsername/demoPassword in the same request, and the review details need an explicit versionString.
store.config.json→store.config.js(EAS's documented dynamic-config path): the demo credentials come fromAPP_REVIEW_EMAIL/APP_REVIEW_PASSWORDat push time — same env varsbun run db:seed-reviewconsumes — so they never enter the public repoapple.version: "1.0.0"pins the version stringeas.jsonmetadataPathupdated
Everything else in the config is byte-identical to the JSON it replaces. Push flow becomes: seed the review account, then APP_REVIEW_EMAIL=… APP_REVIEW_PASSWORD=… eas metadata:push.
Summary by cubic
Switches App Store metadata from static JSON to dynamic store.config.js so eas metadata:push includes required demo credentials and an explicit version string. Previously we pushed demoRequired: true without demoUsername/demoPassword and no apple.version, which ASC rejected; everything else in metadata is unchanged.
- Updates
eas.jsonto pointmetadataPathto./store.config.js; setsapple.versionto "1.0.0". - Reads demo credentials from
APP_REVIEW_EMAILandAPP_REVIEW_PASSWORDat push time so they do not enter the repo. - Rollout: seed the review account, export the two env vars, then run
eas metadata:push(push will fail if the vars are missing).