EAS Update published but the app never picks up the new version

Most likely a runtime version mismatch. An update only goes to builds with the same runtimeVersion. If your build has "runtimeVersion": { "policy": "appVersion" } and you bumped version in app.json after building, the update targets a runtime no build has.

Check on expo.dev → Updates: the update shows its runtime version; compare with the build's. Also note the default behaviour: the app downloads the update on launch and applies it on the next launch, so it takes two cold starts.

If runtime matches, check the build is actually on the production channel: eas build:list shows the channel per build. Builds made before you added channel to eas.json have no channel and never receive updates.

Add a hidden debug screen that calls Updates.checkForUpdateAsync() and shows the result and Updates.channel / Updates.runtimeVersion. Errors from the update check are otherwise swallowed and you're guessing.