Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My React Native app was abandoned and no longer builds

Short answer

An abandoned React Native app usually still has value: the code, the store listing and your users. First secure the source code and the store accounts. Then an engineer checks whether the app can be upgraded step by step or has to be rebuilt. React Native's own guide calls upgrading tricky for apps with Android, iOS and JavaScript parts.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The developer or agency stopped replying and the app has not been updated for a long time.
  • Nobody can make a new build; the project fails with errors on a new computer.
  • The app uses a very old React Native version and the stores want newer ones.
  • Updates break other features, so everyone is afraid to touch it.
  • I am not sure I even have the full source code.

Why does this happen?

  1. A React Native app is three projects in one

    React Native's documentation says a typical project is made up of an Android project, an iOS project and a JavaScript project, so upgrading can be rather tricky. Skip several versions and the gap grows.

  2. Libraries age faster than the app

    Every package the app uses has its own versions. When the developer stops maintaining the app, those packages drift apart until the project no longer builds.

  3. The build only worked on one person's computer

    Node, Java, Xcode and other tools have to match. When that computer is gone, the exact setup is gone too.

  4. The stores keep raising their requirements

    An app that is not rebuilt for years eventually cannot be updated, because new store rules need a newer build.

What can I do about it today?

  1. Find the source codeAsk the developer or agency for the code repository, in writing. Check whether you can see it with your own account.
  2. Open your store accountsConfirm who owns the Apple and Google Play accounts the app is published in. If it is the developer's, see the page on moving an app to a new developer account.
  3. Do not release anything or ask for a rebuild yetA rushed update on an old project can break the working live version.
  4. Collect what you knowLogin details for services the app uses (maps, push, analytics, payments), the server address, and any documents from the old developer.
  5. Write down what must keep workingThe three or four things your users do in the app. That is what a rescue protects first.

When should I bring someone in?

  • The developer has disappeared and you cannot reach the code or the accounts.
  • The store has warned you that the app will stop being available for new users or updates.
  • You have a quote that says rewrite and want a second view before paying.

How do I handle it?

  1. Secure a copy firstCode, assets and configuration are copied to a repository your company owns before anything changes.
  2. Get it to build againI recreate a working build environment, so there is a first proof that the app can be built and run.
  3. Assess upgrade against rebuildI compare the two with what each keeps, what it costs in effort and what risk it carries, and tell you which I would pick.
  4. Upgrade in small, tested stepsReact Native's Upgrade Helper shows the changes between versions, and I move version by version rather than in one jump.
  5. Hand it over with notesYou get a short written guide on how to build, release and who owns what, so the app is not abandoned again.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I have to rebuild the app from scratch?

Not always. React Native documents an upgrade route and a tool that shows the changes between any two versions. Whether that is worth it depends on how far behind the app is and what state the code is in.

What if I do not have the source code?

Then the first job is recovering it from the developer or the app's hosting. If it cannot be recovered, the app has to be rebuilt from what users see. See the page on not having the source code.

Will my users lose the app during a rescue?

The live app stays in the store while I work in a copy. A new version only goes out once it is tested.

Can you also take over future updates?

Yes, as a monthly plan or per task. I quote it after a short discovery call against a written scope.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.