Expo

Get Started
Feature Preview

Over-the-air updates

We're currently working on EAS Update, a service that integrates deeply with other EAS services and builds on top of expo-updates to provide more power, flexibility, and tools to help you work better with your team.
EAS Build includes some special affordances for Expo's over-the-air updates library, expo-updates. 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.

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 release builds, and the "staging" release channel for test builds distributed with internal distribution.
{
  "build": {
    "release": {
      "releaseChannel": "production"
    },
    "team": {
      "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 if when you add or remove a native library, or modify app.json), you should increment the runtime version.