OTA update

Learn OTA (over-the-air) updates.

What is an OTA update?

An OTA (over-the-air) update sends JavaScript changes to the device without store review. Expo Updates provides this; users get the new JS bundle without reinstalling the app.

OTA works only for JS and asset (image, font) changes. If native code (Gradle, CocoaPods) changes, a new store build is required. The eas update command publishes an update; the expo-updates library pulls it on the device. With channels you can send different bundles to different user groups.

The eas update command

The eas update command publishes an update. You set the channel with --branch and a note with --message. Example: eas update --branch production --message "Bug fix".

On the device the expo-updates library checks the server periodically. If a new bundle exists it downloads it and applies it on the next launch. The updates.enabled field in app.json must be true. While testing you can use --branch staging as a separate channel, then move it to production.

Exercise Write the app.json updates section

In an app.json skeleton define the "updates" section. It carries "enabled" set to true and "fallbackToCacheTimeout" set to 0.

Show example solution

{
  "expo": {
    "name": "App",
    "updates": {
      "enabled": true,
      "fallbackToCacheTimeout": 0
    }
  }
}

Test yourself

Which changes cannot OTA send?
```
eas update --branch production
```
- Native code changes
- Text fixes
- Changing the color theme
- Adding a new image
Show answer

Native code changes — Native code changes require a new store build.
Match each flow piece to its role

eas update

Publishes update
--branch

Picks channel
expo-updates

Pulls on device
--message

Writes a note

Write the updates.enabled field

"updates": { "enabled": ____ }

Show answer

"updates": { "enabled": true }

Next lesson: Summary - CI/CD

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies