Get Started

Using expo-updates

This guide references Classic Updates service. As of Dec 2021, we started previewing the next generation of our updates service: EAS Update. Learn more.
EAS Build includes some special affordances for Expo's expo-updates library. In particular, you can configure the release channel in eas.json and EAS Build will take care of updating it in your native project at build time. Not sure what a release channel is? Learn more about release channels. This document covers concerns specific to using expo-updates with EAS Build; for more general information about configuring expo-updates, refer to the "Configuring Updates" guide.

Setting the release channel for a build profile

Each build profile can be assigned to a release channel, so updates for builds produced for a given profile will pull only those releases that are published to its release channel. If a release channel is not specified, the value will be "default".
The following example demonstrates how you might use the "production" release channel for production builds, and the "staging" release channel for test builds distributed with internal distribution.
  "build": {
    "production": {
      "releaseChannel": "production"
    "preview": {
      "releaseChannel": "staging",
      "distribution": "internal"

Your native runtime may change on each build, depending on whether you modify the code in a way that changes the API contract with JavaScript. If you publish a JavaScript bundle to a binary with an incompatible native runtime (for example, a function that the JavaScript bundle expects to exist does not exist) then your app may not work as expected or it may crash.
We recommend using a different runtime version for each binary version of your app. Any time you change the native runtime (in managed apps, this happens when you add or remove a native library, or modify app.json), you should increment the runtime version.

Updates published with the runtimeVersion field can't be loaded in Expo Go; instead, you should use expo-dev-client to create a development build.

Environment variables set on the env field in build profiles are not available when you run expo publish. Learn more in the "Environment variables and secrets" guide.