Expo Documentation
docs.expo.dev › deploy › send-over-the-air-updates
Send over-the-air updates - Expo Documentation
Learn how to send over-the-air updates to push critical bug fixes and improvements to your users.
Videos
02:42
When to use over the air updates | Three important OTA use cases ...
09:06
How to use over the air updates to share previews with your team ...
02:24
EAS Update + Github = Automatic OTA updates | Live Expo Demo - YouTube
03:16
Expo Golden Workflow: Share preview updates with your team - YouTube
03:29
Golden Workflow: Deploy your app to production with an automated ...
Reddit
reddit.com › r/reactnative › expo "over the air update" is awesome
r/reactnative on Reddit: Expo "Over The Air Update" Is Awesome
September 22, 2024 -
Just tired and implemented the expo OTA. It's great and I really enjoyed. This one reason is enough for me to prefer it over Flutter. 😅
Top answer 1 of 5
14
It's crazy expensive, I'd only ever push an update there in an emergency
2 of 5
9
OTA’s are great but remember these take an initial app launch to download, and another app launch to kick in (I.e first time installs from the App Store won’t have the OTA yet ) You can delay the UI and relaunch the app manually after it downloads but depending on the devices network, this can take 30 seconds and destroy a very important part of the mobile-apps UX ( it can also fail to download for xyz reasons ) TLDR: over the air updates are awesome but binary updates are preferred in 95% of enterprise use cases
GitHub
github.com › axelmarciano › expo-open-ota
GitHub - axelmarciano/expo-open-ota: An open-source self-hosted custom updates server implementing the Expo Updates protocol, built for production. Supports cloud storage & CDN.
🚀 An open-source Go implementation of the Expo Updates protocol, designed for production with support for cloud storage like S3 and CDN integration, delivering fast and reliable OTA updates for React Native apps.
Starred by 176 users
Forked by 23 users
Languages Go 46.1% | TypeScript 39.1% | MDX 10.5% | JavaScript 2.5% | CSS 1.1% | Smarty 0.3%
GitHub
github.com › xavia-io › xavia-ota
GitHub - xavia-io/xavia-ota: A self-hosted Over-The-Air (OTA) updates server for Expo/RN applications that gives you complete control over your app's update distribution.
A self-hosted Over-The-Air (OTA) updates server for Expo/RN applications that gives you complete control over your app's update distribution. - GitHub - xavia-io/xavia-ota: A self-hosted Over-The-Air (OTA) updates server for Expo/RN applications ...
Starred by 368 users
Forked by 48 users
Languages TypeScript 94.6% | Shell 2.4% | JavaScript 2.2%
YouTube
youtube.com › watch
Sending Over-the-Air (OTA) Updates with EAS Update | Step-by-Step Guide - YouTube
In this tutorial, we dive into EAS Update for over-the-air (OTA) updates in Expo. Key topics include runtime version, EAS CLI setup, EAS Build configuration,...
Published November 6, 2024
DEV Community
dev.to › jocanola › zero-downtime-deployment-master-over-the-air-ota-updates-in-expo-react-native-4p8a
Zero-Downtime Deployment: Master Over-the-Air (OTA) Updates in Expo React Native - DEV Community
October 24, 2025 - In simple terms, OTA updates let you deliver new JavaScript code, images, and other assets directly to users’ devices—without going through the app store review process. It’s like refreshing a web page, but for your mobile app. With Expo’s EAS Updates, this process becomes seamless, secure, and fully integrated into your deployment workflow.
npm
npmjs.com › package › expo-updates
expo-updates - npm
» npm install expo-updates
Published Jul 08, 2025
Version 0.28.17
Author 650 Industries, Inc.
Repository https://github.com/expo/expo
Reddit
reddit.com › r/expo › i have a question about expo ota updates and app version
r/expo on Reddit: I have a question about Expo OTA updates and app version
1 month ago -
Hi
In my eas.json, I have this under build:
"production": {
"channel": "production",
"distribution": "store",
"environment": "production",
"autoIncrement": true,
"ios": {
"simulator": false
}
}I have a question about OTA updates.
Let's say I have an app version 1.0.0 and some users are using it. Then I upload a new version 2.0.0 and some users update and use it (so now I have users using 2 different versions).
How can I send an update to the ones on the older version since all the users are on the same production channel? Is there any way to send an OTA update to the users on one version and not the others?
Thanks
Top answer 1 of 5
2
This is a solid question! Why not just push an update prompt so users can open the app -> see the update prompt -> update the app instead of updating version 1.0 ?
2 of 5
2
We moved off of expo and started delivering our own bundles so my info is out of date, but they used to have you specify a runtime version to prevent delivering OTA updates to incompatible apps.