</>SkillRecallRECALL WHAT YOU KNOW
Prepare for an interviewExplore Library
ExpoOver-the-Air (OTA) Updates with EAS Update

7 items

1

Runtime Version Policy Breaks OTA

Code Quiz
2

Runtime Version & Channel Update Delivery

Quiz
3

Runtime Version Gates OTA Updates

Slides / Video
4

Runtime Version & Channel Compatibility

Flashcard
5

Runtime Versions and Native Code Changes

Quiz
6

EAS Update & the OTA Delivery Model

Slides / Video
7

EAS Update & OTA Delivery Model

Flashcard
Quiz

Runtime Version & Channel Update Delivery

Understanding why an EAS Update reaches some builds but not others based on runtime version compatibility.

Your app is on the 'production' channel. You add a new native library, bump the build, then run `eas update --branch production` to push a JS-only bugfix. Existing users on the OLD production build do NOT receive the update, even though the branch and channel are correct. Assuming your runtimeVersion policy is not causing an accidental match, what is the most likely explanation?