Using EAS Update
EAS Build includes some special affordances for Expo's
library. In particular, you can configure the
property in eas.json
and EAS Build will take care of updating it in your native project at build time. Not sure what a channel is? Learn more about channels
. This document covers concerns specific to using
with EAS Build; for more general information about configuring the expo-updates library with EAS Update, refer to the EAS Update getting started doc
Each build profile
can be assigned to a channel, so updates for builds produced for a given profile will pull only those releases that are published to its channel.
The following example demonstrates how you might use the
channel for production builds, and the
channel for test builds distributed with internal distribution
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
field can't be loaded in Expo Go; instead, you should use expo-dev-client
to create a development build.