Skip to content
All insights

Mobile Development

Expo Staging and Production Environments With Supabase

Set up Expo staging and production with Supabase. Align EAS Build profiles, update channels, and backend targets with a mobile release checklist.

Give your Expo staging build its own update channel, EAS environment values, and Supabase project. Then verify the installed build and an over-the-air update on a device. A staging binary can receive the expected update while the new JavaScript bundle points its requests at production. Testing both is what catches the mistake before a tester writes live data.

Key takeaways

  • Align the build profile, update channel, runtime version, and backend for each release target.
  • Use separate Supabase projects for preview and production, with test accounts and destinations in preview.
  • Verify the backend after a fresh install and again after the staging update is running.
Applying this to your product?Discuss your Expo release setup

What the new Expo and Supabase integration sets up

On November 10, Supabase announced an EAS CLI integration that provisions a project, adds the Supabase client SDK, and configures its connection values in Expo. The announcement calls for EAS CLI 21.8.0 or later and an Expo-linked project. For a new integration, the documented command is eas integrations:supabase:connect. The initial connection can populate multiple environments with one project. The --environment preview option sets up a separate preview connection.

If the app is already live, first inventory the existing project references and owners. Plan any change to environment values around testers and deployed copies. Seed synthetic records and configure the preview auth redirects, notifications, and other integrations the app needs.

Supabase’s November 10 announcement for the Expo integration

Expo’s setup guide for using Supabase

Map each install to a channel and backend

An EAS Build profile defines how you make the binary. Its channel tells copies of that binary where to look for updates. Its environment selects configuration values during the build. Runtime version compatibility determines which update a build can load. If testers need both apps on one device, give the staging app a separate bundle identifier or package name and configure matching app links, auth, and credentials.

Illustrative deployment map for an Expo booking app
InstallBuild profile and update channelEAS values and backend
Developer builddevelopment profile, local bundler during normal developmentdevelopment values and a local or development backend
Staging buildstaging profile, staging channelpreview environment and its own Supabase project
Store buildproduction profile, production channelproduction environment and the live Supabase project

Expo’s environment-variable behavior for builds and updates

Publish the update with the matching environment

Imagine the booking app’s staging binary starts on the preview database. A later update is published to the staging channel with production environment values. If the runtime matches, the binary can accept it. The new bundle can then make requests using the inlined production URL. A successful upload tells you the bundle was published. The device check tells you where requests actually go.

In the command below, staging is the update channel and preview is the EAS environment. Expo requires the environment flag for EAS Update on SDK 55 and later. Record the source commit, update group, and runtime. If preview and production endpoints are compiled into their respective bundles, build the production update from the tested commit with production values. Republishing the staging bundle would carry the values already in its JavaScript.

Example staging update command

Run from the intended commit once you have verified the staging channel and preview environment.

eas update --channel staging --environment preview --message "Verify staging booking flow"

Expo’s update deployment patterns and runtime guidance

FROM READING TO DOING

Make your Expo release targets easier to verify

Share your current EAS profiles, Supabase projects and the flows your testers need. We can help map the right targets and test them on iOS and Android.

Verify isolation from the installed app

Record the active update identifier and expected backend project reference in an internal diagnostics screen or test log. Create a synthetic booking in staging and confirm the record in the preview project’s server-side logs or database. Repeat after the remote update has applied. Use read-only diagnostics or an approved synthetic smoke test for production.

  • Install staging on iOS and Android. Confirm the channel, runtime and project reference before sign-in.
  • Sign in through the preview auth route, make a synthetic booking, and verify that any email, push or payment action goes to its sandbox destination.
  • Apply the staging update. Record the active update ID and repeat backend and booking checks.
  • Confirm the production candidate’s runtime and backend separately, and keep privileged keys in server-side configuration.

Plan native and update compatibility checks for Expo SDK 58

Keep a recovery path for the compatible runtime

Record the known-good update group, runtime, and environment before releasing. If an update routes to the wrong backend, pause further rollout and recover using your documented update pattern. Test the recovery on a device with the affected runtime. Review any messages, payments, or writes that already occurred, and assign an owner to resolve them. When the fix requires a change to native code, verify a new binary through the store release process.

Frequently asked questions

Can staging and production use the same EAS environment?

They can share values when the team intentionally wants the same backend and settings. If staging needs to exercise writes safely, select a separate environment with preview backend values and sandbox integrations.

Can I promote the exact staging update to production?

Use the same bundle when its compiled configuration and signing setup suit both targets. If it includes a staging backend URL, publish a new bundle from the same reviewed commit using production environment values, then verify the production runtime.

YOUR NEXT STEP

Let’s work through your next step.

Tell us what you’re building, what you’ve tried, and where you need a hand. We’ll work with you to define a practical way forward.

Keep reading.

Choose which optional tools can run. You can reopen these settings from the footer. These choices do not subscribe you to marketing emails.

Cookie Policy