Working with Expo?

EAS Build red or Expo updates not landing? We ship it properly.

Expo turned React Native from a toolchain puzzle into something a small team can actually ship. Then EAS Build starts failing on a new Xcode, an OTA update refuses to land on half the installs, and the config plugin for one native module quietly breaks the iOS pod install. We work the EAS logs, the app config and the native prebuild until the build is green and the right update reaches the right devices.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

eas-build.log

still failing

What it is

Expo at a glance

Expo is a framework and cloud platform around React Native, created by the company Expo Inc., with the SDK first released in 2016. It provides a managed set of libraries that cover most mobile features without writing Swift or Kotlin, a build service called EAS Build, a submission service called EAS Submit, and an over-the-air update service called EAS Update.

Modern React Native projects almost all start with Expo now, because the alternative is running the Metro bundler, Xcode and Android Studio by hand and keeping three toolchains aligned forever. Expo Router has become a common pick for file-based navigation, and config plugins let managed projects add native code without dropping to the bare workflow.

Type
React Native framework and build cloud
First released
2016
License
MIT (open-source SDK), commercial for EAS
Maintained by
Expo, Inc.
Typically used for
React Native apps for iOS and Android, cross-platform mobile, Expo Router based navigation, OTA update flows

The honest version

Expo pros and cons

No technology is all upside. This is where Expo earns its place and where it tends to cause trouble.

Where Expo is strong

  • A ready-made native toolboxCamera, notifications, secure storage, biometrics, location, media and sensors come as first-party libraries. A new project ships with most of what a consumer app needs without writing any native code.
  • EAS Build removes the Mac problemiOS archives come out of a cloud Xcode runner rather than a laptop in the office. Signing certificates are managed through Expo's credentials service, which removes a class of problem that used to eat days.
  • Over-the-air updates for JavaScriptEAS Update ships JavaScript and asset changes to installed apps without going through the stores, which turns a hotfix for a logic bug from a day into an hour.
  • Config plugins for native modulesManaged projects can add third-party native modules through plugins that run at prebuild time. The project stays managed while the capability grows.
  • Expo RouterFile-based navigation that mirrors Next.js conventions, with typed routes, nested layouts and a learning curve shorter than React Navigation's imperative API.
  • A steady release cadenceSDK releases roughly every six months with clear migration notes. Projects that stay on current SDKs rarely hit the walls that pile up on abandoned React Native setups.

Where Expo bites

  • EAS Build has its own failure modesCloud runners mean cloud log files, slow iteration on signing issues, and queue times that spike before store deadlines. The build platform helps and then it is where the problem is.
  • OTA updates need disciplineNative code changes still require a store release, but plenty of changes shade between native and JavaScript. Shipping an update that references a native API not in the installed binary silently breaks the app on launch.
  • The managed to bare transition is one-wayA project that ejects to the bare workflow gives up the managed story and takes on native projects for iOS and Android. The decision is not casual, and some teams make it too early.
  • Config plugins are a growing areaNot every native library ships a plugin. When one does not, the choices are writing a plugin, maintaining a fork, or going bare, none of which are small.
  • EAS is a paid service past a pointThe free tier covers hobby and small-team use, but production workloads with many builds, many updates, and multiple apps add up quickly. Budget realistically.
  • Store rejections still arriveApple's privacy manifests, background mode justifications and child-safety rules apply the same way as a native app. Expo makes submission easier but does not make the rules go away.

Sound familiar?

Common Expo problems we fix

The Expo problems that bring people to us, and what you have once each one is fixed.

No profiles for 'com.myapp' were found

EAS iOS build fails on provisioning

A certificate that expired overnight, a bundle identifier that differs between app.json and the Apple account, or a provisioning profile that was revoked during a developer program renewal.

Credentials valid and reproducible

CocoaPods could not find compatible versions for pod "ExpoModulesCore"

Pod install breaks on prebuild

An SDK version that does not match the installed Expo modules, usually after a third-party plugin brought in a newer ExpoModulesCore than the project is on.

Pods resolve against the current SDK

expo-updates: no update available (channel mismatch)

Over-the-air updates do not reach devices

A channel configured in app.json that does not match the channel the update was published to, or a runtime version mismatch between the binary and the update that silently filters the update out.

Updates land on the right binaries

Gradle task :app:bundleReleaseJsAndAssets failed

Android release build fails on bundling

A Metro error that only shows up in release mode, usually a dynamic require, a missing asset extension in the config, or a native module that was not properly linked by the config plugin.

Android release bundle produced cleanly

Expo config plugin 'expo-camera' is out of date

A plugin blocks an SDK upgrade

A third-party or in-house plugin that has not caught up with the current SDK and refuses to apply at prebuild. The project cannot move forward until the plugin does.

Plugins in sync with the SDK

app.json ios.bundleIdentifier differs from the Xcode project

Managed and bare workflow configs disagree

A project that was partially ejected, leaving ios/ and android/ folders that drift from app.json. Prebuild stops regenerating them cleanly and nobody is sure which is authoritative.

One source of truth for configuration

Fastlane build failed with status code 65

Xcode build fails on a new iOS version

A new Xcode major release broke a pod, deprecated an SDK target, or changed a signing default. EAS runs the new Xcode as soon as Apple does, so the failure shows up on the first build after release.

Build green on the current Xcode

Invalid Provisioning Profile. The provisioning profile is expired

EAS Submit rejected the upload

Credentials rotated in Apple's dashboard without updating the Expo credentials, a profile revoked after a team change, or a push certificate that expired without a renewal reminder.

Submission accepted and tracked

What we do

Expo help, from rescue to ongoing care

Call us about one failing EAS build, or hand over the Expo project and we take it end to end.

Rescue
Builds that will not go green, updates that never land, submissions that keep bouncing. We get the pipeline producing shippable binaries before explaining the cause.
EAS Build and credentials
Signing certificates, provisioning profiles, keystores and credentials service reviewed, with clear documentation so a certificate rotation is not an emergency next time.
Over-the-air updates
Channels, runtime versions and rollback strategy worked out so an OTA update reaches the right installs and a bad update can be pulled in minutes rather than hours.
SDK upgrades
Expo SDK bumps with config plugins reviewed, native modules swapped where needed, and the app tested on physical devices before going into the store.
Managed to bare moves
Honest conversations about whether a project needs to leave the managed workflow, and clean execution when the answer is yes.
Managed Tech
Steady work on SDK updates, certificate renewals, store submission support and the regular maintenance that keeps a cross-platform mobile app shippable on both stores.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Expo alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Expo questions

Something else? Call+1 737 727 7327

Should we stay on managed Expo or move to the bare workflow?

Stay managed whenever a config plugin can do what you need. The bare workflow gives you full access to the native projects but trades the entire managed story for that access. Teams that eject for one feature often spend the next year maintaining native projects they did not plan to own. We assess the specific blocker and only recommend ejecting when a plugin is genuinely not possible.

Why do our Expo OTA updates not reach devices?

The common causes are a channel mismatch between the published update and the app binary, a runtime version that is incremented in one place but not another, a release channel that was renamed without updating the app configuration, or an update that references a native API not present in the installed build. We trace the update manifest the device actually fetches and find the specific filter rule that excluded it.

How do we fix an EAS Build that fails on Xcode updates?

By rebuilding the toolchain against the new Xcode on a branch, bumping the pods that have caught up, patching or forking the ones that have not, and verifying the archive on a physical device before merging. EAS keeps an older Xcode image for a window after a release, which buys time to stabilize before the rollover is mandatory.

Can you take over an Expo project from a previous developer?

Yes, this is a common request. We take inventory of the app.json configuration, the credentials in EAS, the store listings and any native customizations, get the project building on our machines, and move ownership of every account into your name before writing code.

Is Expo production-ready for a serious app?

Yes, and many apps with millions of installs run on managed Expo. The decisions that matter are picking the right SDK release to pin against, writing OTA update discipline into the deploy process, and keeping config plugins current with the SDK. Teams that skip the discipline run into trouble whatever framework they pick.

How much does Expo help cost?

The estimate is free of charge. Describe the app and where the pipeline is breaking, and a price comes back ahead of any work.

Free estimate

Expo app giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.