Skip to content

mobile: point staging at the self-hosted OTA backend #8795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aapeliv merged 1 commit into from
May 24, 2026
Merged

mobile: point staging at the self-hosted OTA backend #8795

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions app/mobile/app.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,12 +76,17 @@ const intentFilters = variant.linkHost

// Dev Tool branches load OTA through the dev launcher's deep-link load path
// (couchers-devtool://expo-development-client/?url=...), so no update URL is
// baked in and manifests are served unsigned over HTTPS. Staging and production
// stay on EAS Update.
// baked in and manifests are served unsigned over HTTPS.
//
// Staging points at our self-hosted OTA backend (cut 1: validating the Expo
// Updates protocol + native<->backend transport, unsigned). Production stays on
// EAS Update until staging is proven, then flips here too.
const updates =
APP_VARIANT === "devtool"
? { enabled: true }
: { url: "https://u.expo.dev/fb4fc9aa-d8b2-45a5-82aa-be05e99b0413" };
: APP_VARIANT === "staging"
? { url: "https://dev-api.couchershq.org/mobile/ota/manifest" }
: { url: "https://u.expo.dev/fb4fc9aa-d8b2-45a5-82aa-be05e99b0413" };

export default {
name: variant.name,
Expand Down
Loading