Home › Build error fixes › CI (GitHub Actions, EAS, fastlane)

expo-updates is installed but not configured

CI (GitHub Actions, EAS, fastlane) · last reviewed 2026-11-10

The error looks like this

expo-updates module is not configured. Please run "eas build:configure" first to configure the project

Why it happens

The native project is missing the expo-updates build phase or the updates URL / runtime version.

How to fix it

  1. Run: eas update:configure (older CLIs: eas build:configure).
  2. Bare projects: then cd ios && pod install, and commit the changes.
  3. Not using OTA updates? Remove expo-updates instead: npm uninstall expo-updates.

Not sure this is your error? Let ReleaseMedic read the whole log

Build logs are long and the last line is rarely the real cause. ReleaseMedic finds the first real error, explains it and gives the steps — free, and the log never leaves your computer.

$ npx releasemedic log build.log

Or pipe a build straight in: cd android && ./gradlew bundleRelease 2>&1 | npx releasemedic log -

Catch it before you build

Most release errors come from project settings you can check in seconds — signing, SDK levels, privacy manifests, permissions, push and login setup.

$ npx releasemedic

Related CI (GitHub Actions, EAS, fastlane) errors