Questify

4.5.1

Released

Nothing in this release changes what you see; it is all under Technical changes.

Technical changes· 2 entries for database, tooling, CI, tests and docs

Tooling & Configuration

  • A store that refuses a mobile submission no longer stops the release's over-the-air update. The Mobile build run asked for its builds with eas build --auto-submit, which checks every store's submission credentials inside the build request; on the 4.5.0 merge EAS held no Play service account key for submissions, so the request failed after both builds were queued, and the OTA update and the Sentry source-map upload after it never ran. The request now only builds, and a new last step, Submit to the stores (apps/mobile/scripts/eas-submit-builds.mjs), submits each requested build by id with eas submit --id … --non-interactive --no-wait, one platform at a time, when MOBILE_AUTO_SUBMIT is true. A refused platform fails that step with the credential it needs, after the update and source maps have gone out and after the other platform has been tried. docs/mobile/release.md says which eas credentials slot holds the Play submission key (#1224).

Tests

  • eas-submit-builds.test.mjs covers the submission plan from eas-cli 26's build output (a build per platform, anything else skipped), the eas submit arguments and the summary's hint for a refused platform; workflow-triggers.test.mjs pins that the build request no longer auto-submits and that submission is the last step, after the source maps, gated on the request and MOBILE_AUTO_SUBMIT (#1224).