mobile: point staging at the self-hosted OTA backend#8795
Conversation
Set the staging variant's updates.url to the backend's /mobile/ota/manifest endpoint (unsigned, cut 1) to validate the native<->backend OTA transport on a real build. Production stays on EAS Update until staging is proven. The backend endpoint itself is in a separate PR against develop. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Preview buildsMobile Dev Tool previewScan the QR with your phone camera, or tap Open in Dev Tool on the device, to open this branch in the installed Dev Tool dev client. ios — Open in Dev Tool Deep linkandroid — Open in Dev Tool Deep linkcommit |
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR is a staging-only configuration change for the mobile app's OTA update backend. It does not directly affect end users yet, adds no visible feature, and is primarily internal infrastructure validation rather than a broadly user-noticeable improvement. 🤖 Bot Debug InformationModel: |
2 participants
Points the staging Expo app variant at our self-hosted OTA manifest endpoint (
https://dev-api.couchershq.org/mobile/ota/manifest) instead of EAS Update. This is cut 1 of validating the self-hosted Expo Updates protocol and the native↔backend transport (unsigned).The Dev Tool variant keeps its dev-launcher deep-link path, and production stays on EAS Update until staging is proven — then production flips here too.
This branch is rebased onto
mobile/v1.1.20; it is a single one-line config change on top of that base (the rest of the Dev Tool OTA work already landed inv1.1.20).Testing
Ran from
app/mobile:npm run lint(expo lint) — cleannpx tsc --noEmit— no type errorsnpm test(jest) — 129/129 tests passStill needs on-device validation: install a staging build and confirm it fetches/applies an update from the self-hosted manifest endpoint.
For maintainers
This PR was created with the Couchers PR skill.