Working with React Native?

React Native build broken or app rejected? We ship it.

Most React Native projects that reach us build fine on the laptop that first set them up and fail everywhere else. We get your build green on a fresh machine, get the binary past review, and leave notes the next person can actually follow.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

metro.log

still failing

What it is

React Native at a glance

React Native is Meta's framework for building iOS and Android apps with React, first released in March 2015. Code is written in JavaScript or TypeScript and renders to real native UI components through a bridge, or through the newer Fabric renderer on recent versions.

It powers a long list of well-known apps, including Meta Messenger, Shopify, Discord and parts of Microsoft Office. Most teams start with Expo, an independent company that offers a managed workflow and a hosted build service called EAS, which hides the Xcode and Android Studio setup until you need it.

Type
Mobile framework
First released
2015
License
MIT
Maintained by
Meta and open-source contributors
Typically used for
iOS and Android apps sharing one codebase, companion apps to React web products, SaaS mobile clients

The honest version

React Native pros and cons

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

Where React Native is strong

  • One JavaScript codebase for both storesThe same code ships to iOS and Android, and with extra effort to Windows and macOS, so a small team can cover every platform your customers are on.
  • A huge React talent poolAnyone who already knows React on the web is most of the way to being productive here, which makes hiring and handover much easier than with a platform-specific stack.
  • Expo makes onboarding painlessA new developer can clone the repo, install dependencies, and run the app on a real phone within an hour, without touching Xcode at all on day one.
  • Fast iteration with Fast RefreshEdits to a component show up on the running app within a second, keeping the feedback loop closer to web work than to a traditional native build.
  • Native modules when you need themAnything the framework does not cover can be bridged to Swift, Kotlin or C++, so you are never fully blocked by the JavaScript side.
  • Mature library ecosystemReact Navigation, Reanimated, Redux and Tanstack Query are stable, well-documented and used at scale, so you rarely have to invent the plumbing yourself.

Where React Native bites

  • The native toolchains go stale fastXcode and the Android SDK ship new required versions every year, and an app that built fine last summer often will not build at all this summer without updates.
  • Store policy keeps changingApple adds purpose string requirements, Google sets target SDK deadlines, and missing either one blocks the release until the project is updated.
  • Version upgrades are painfulMoving a project from 0.68 to 0.74 touches nearly every config file, and the official upgrade helper is a starting point rather than a finish line.
  • Third-party native modules go abandonedA library that was the obvious choice three years ago is often unmaintained now, and replacing it is a real piece of work, not a one-line change.
  • Expo managed and bare are a forkSwitching between them later costs real time, and the right pick depends on whether you need custom native code now or in a year.
  • Native crashes mean native toolsA crash that only shows up on a real device sends you into Xcode or Android Studio, reading stack traces that look nothing like a JavaScript error.

Sound familiar?

Common React Native problems we fix

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

Gradle build failed

The build stopped working

Usually the Android SDK, Java version or an abandoned native module has moved on since the project was last touched, and the lockfiles no longer agree.

Green builds on a fresh laptop

ITMS-90683

The App Store rejected the release

A missing purpose string, a privacy manifest that is out of date, or a Guideline 4.3 spam notice on a template-looking app.

Approved on the next submission

targetSdkVersion 34 required

Google Play is about to pull the app

Play policy requires a recent target SDK each year, and missing the deadline hides the listing from new installs.

Target SDK raised, listing live

0.68 and nobody has touched it in two years

The version is far behind

Every dependency has moved on, the build tools have moved on, and nobody wants to be the one to start.

On a current version, with notes

provisioning profile expired

Nobody can produce a build

Certificates have expired, the Apple Developer account is in someone's personal name, and the keystore for Android is nowhere obvious.

Signing credentials back in order

RedBox on launch

A native module crashes on startup

A library that stopped being maintained is calling APIs that no longer exist, and the app shows a red screen the moment it opens.

Replaced or patched, app opens clean

What we do

React Native help, from rescue to release

Call us for one broken build, or hand us the whole app.

Rescue
Builds that fail, releases that bounce back from review, apps that won't launch on a current OS.
Upgrades
Moving between React Native versions and Expo SDKs, with the project still shipping along the way.
Takeover
Picking up an app from a previous developer, including certificates, keystores and store accounts.
Store submissions
Preparing binaries, writing the review notes, and handling the back and forth with App Review.
Custom work
Features, native modules and integrations built so the next person on the project can follow them.
Managed Tech
Keeping the build working as toolchains and store policies change, on an ongoing basis.

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 React Native alongside something else?

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

Questions

React Native questions

Something else? Call+1 737 727 7327

Our React Native build stopped working, can you fix it?

Yes, that is the single most common reason teams call us. We usually find a mix of expired certificates, a Java or Xcode version that has moved on, and one or two native modules that are no longer maintained. We get the build green on a fresh machine and write down what changed so it does not happen the same way twice.

Can you take over a React Native app from a previous developer?

Yes. We go through the repository, the Apple Developer and Google Play accounts, the signing credentials and any Expo or EAS project, and hand you a short written inventory of what you own, what is missing, and what we had to replace.

How do we upgrade our React Native app to the current version?

Step by step and on a branch, not in one jump. We use the official upgrade helper as a starting point, then work through the config files, the native modules and the build scripts by hand, with the app still running against your staging backend the whole time.

Our app was rejected by the App Store, can you help?

Yes. Most rejections we see are missing purpose strings, outdated privacy manifests, or a Guideline 4.3 note on something that looks too much like a template. We read the actual rejection, fix the underlying cause, and resubmit with notes written for the reviewer.

Should we move from Expo managed to bare, or the other way?

It depends on whether you need custom native code and how much your team wants to touch Xcode. For most teams the managed workflow with EAS is the right starting point, and only specific features push a project into the bare workflow. We will tell you plainly which side your app belongs on.

Free estimate

React Native 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.