EAS Build and Over-the-Air Updates in React Native

"React Native for Beginners" chapters 15/16 showed the MANUAL store publishing process. EAS (Expo Application Services) automates the entire build and distribution process – the direct equivalent of "React for Professionals" chapter 46 (npm run build), just for native app binaries instead of a static web bundle.

Installing the EAS CLI and configuring the project

npm install -g eas-cli
eas login
eas build:configure

eas build:configure creates an eas.json configuration file with sensible default profiles (development, preview, production).

Starting a production build

eas build --platform android --profile production
eas build --platform ios --profile production

The build runs on Expo's CLOUD infrastructure (no local Xcode/Android Studio needed) and produces a finished .apk/.aab (Android) or .ipa (iOS) – upload the result directly to Google Play Console / App Store Connect, right at the point where "React Native for Beginners" chapters 15/16 described the manual build process.

The real novelty: over-the-air updates

Store reviews (see "React Native for Beginners" chapters 15/16/17 for the various distribution paths) often take hours to days – going through that process for EVERY tiny JavaScript bugfix is impractical. expo-updates lets you distribute NEW JavaScript code (not native code!) directly to already-installed apps – WITHOUT a store review.

npx expo install expo-updates

eas update:configure
eas update --branch production --message "Bugfix: cart badge not updating correctly"

On the next app start (or on a manual update check, depending on configuration), the already-installed app downloads the new JavaScript bundle and applies it – your users get the bugfix without having to reinstall the app from the store.

Achtung: OTA updates work EXCLUSIVELY for JavaScript/asset changes – NOT for changes to native code (e.g. ADDING a new native library like react-native-gesture-handler from chapter 10 requires a fresh full store build). Apple's App Store guidelines also EXPLICITLY forbid using OTA updates to change the app's CORE functionality without Apple being able to review that as part of a regular review – use OTA updates for bugfixes and small improvements, not for fundamental feature changes.

Bonus: rolling back a broken update

eas update:list --branch production

Shows all published updates with their IDs – a broken update can be reverted by republishing an EARLIER, known-working version, also without a store review, often within minutes instead of days.

Tipp: Rule of thumb: EAS Build for ANYTHING requiring a new store listing/version number (new native dependencies, larger feature releases). EAS Update for quick JavaScript bugfixes between regular store releases. Combining both tools is the modern standard workflow for professional Expo apps – considerably faster than the purely manual process from "React Native for Beginners".