This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Using Expo Update without other Expo Services

Edit page

Learn how to use Expo Update independently of other Expo Services, such as Expo Build.


Expo Update works great as a standalone service, so you can use it with or without Expo Build and other Expo Services. All of its main features are designed to be agnostic of the build pipeline, and its used in production by large organizations that do not use other Expo Services.

What are the downsides of using Expo Update without other Expo Services?

Expo Update and Build work closely together to provide an experience that is greater than the sum of its parts. For example, when you create a build with Expo Build we will help with the bookkeeping for various aspects related to updates, such as the runtime version and channel.

Builds that use the same channel and runtime version are grouped into a Deployments section on expo.dev. These sorts of bookkeeping and insights features that depend on knowledge of builds or other aspects of your app won't be available if you use Expo Update independently of other Expo Services.

That said, many organizations are already heavily invested in their CI/CD infrastructure or may have other reasons for wanting to use another build pipeline, and the benefits offered by deeper integration across Expo Services may not be worth the switching costs of migrating to a different CI/CD provider.

Using Expo Update without Expo Build

Most of the installation and configuration steps are identical whether or not you use Expo Build. The primary difference is how the update channel is configured. When using Expo Build, the channel from eas.json will automatically be added to your build's AndroidManifest.xml and Expo.plist at build time. When not using Expo Build, this must be configured manually by setting the request header in the app config, followed by manually creating the channel on the server.

Terminal
# Create a channel named `production` (for example, which points to the production Expo Update branch by default)# Your channel names may vary depending on release process
- eas channel:create production