App Developer Disappeared? How to Take Back Your App
Taras Pavlyshyn
Updated · 6 min read
If your app developer or agency has disappeared, secure access before you touch the code, in this order: your Apple and Google developer accounts, the Android signing key, the code repository, the backend and analytics, then the build pipeline. Code can be rebuilt. A lost store account or signing key can cost you the listing, its reviews and future updates.
Why access comes before code
A missing developer feels like a code problem. It rarely is. Code can be read, fixed or, in the worst case, rebuilt from the app that is already in the stores. What cannot be rebuilt is the right to publish: the developer account the app lives in, and the key that proves an Android update comes from the same publisher as the original.
So the first week is not about bugs. It is about making sure that everything an update depends on is in your name, documented, and reachable without asking anyone.
The recovery checklist, in order
| What to secure | Why it matters | What to ask for |
|---|---|---|
| Apple Developer account | The app, its reviews and its bundle ID live here | Account Holder access, or a transfer to your account |
| Google Play developer account | Same for Android: users, ratings, store listing | Owner access, or a transfer to your account |
| Android signing key | Without it you cannot ship an update to the same listing | Whether the app uses Play App Signing; the upload keystore and its passwords |
| Code repository, with history | History explains why the odd-looking workarounds exist | The repo moved into your GitHub, GitLab or Bitbucket organisation |
| Backend and data projects | Firebase, the API server, analytics, crash reporting | Owner roles for your company account on each project |
| Domains, email and push credentials | Password resets, deep links and notifications depend on them | DNS registrar access; the APNs key; the Firebase Cloud Messaging setup |
| Build pipeline and secrets | A pipeline that only runs for them is not yours | Automated build (CI) configuration in your repo; every secret listed and rotatable |
Work down the list. If a step is blocked, the ones above it still decide whether you can publish next week.
What if the app is in the agency's developer account?
Then you need an app transfer, and both stores support it. It is started from the account the app is in now: by its Account Holder on the App Store (Apple: overview of app transfer) and by its owner on Google Play (Play Console Help: transfer apps). Reviews, ratings and users stay with the app; a few services, such as push notifications, are set up again afterwards. Steps, criteria and what to prepare: how to transfer an app to your own developer account.
If the agency will not start the transfer, that is a contract question, not a technical one. Check what your agreement says about ownership of the app and the accounts before anything else. This is general guidance, not legal advice — for a dispute, talk to a lawyer.
What if the Android signing key is lost?
It depends on one setting.
- The app uses Play App Signing (most recent apps do). Google holds the app signing key; the developer only holds an *upload* key. A lost or compromised upload key can be reset: you create a new one and request the reset in Play Console (Play Console Help: Play App Signing).
- The app manages its own signing key. Google is explicit that a self-managed key "cannot be reset if you manage it yourself and lose it". The way forward is then a new listing, which starts without the old one's reviews and installs.
Ask the old team which of the two applies before anything else. On iOS, certificates and provisioning profiles can be regenerated from the account, which is why the account matters more than any file.
What if you don't have the source code?
Ask for it in writing, quoting your contract. If it does not arrive, you still have three things: the build that is live in the stores, the designs, and the backend. That is enough for a new team to rebuild the app — but it is the most expensive path, so it should be a decision, not a reflex.
The same goes when the code arrives in poor shape. "Rewrite everything" is what a new team says when it has not read the code yet. A proper review ends with a written verdict per part of the app — keep, fix, refactor or rewrite, and why. How that decision is made: fix, refactor or rewrite an inherited app.
What to ask the next team
Before you hire anyone to take over, four answers tell you whether you are about to repeat the problem:
1. Will you work in my repository and my store accounts from day one? If the answer is no, you are building the next lock-in. 2. What will you check in the first week, and what do I get at the end of it? You want a written list, not a promise — here is what a takeover check should cover. 3. How will I see progress? Test builds you can install on your own phone beat status reports. 4. What happens if we stop working together? The honest answer is: nothing breaks, because everything is already yours.
How we take over an app
DriveCode builds iOS & Android apps, Flutter-first. When we take over an app, we start with access: the accounts, keys, repository and backend move into your name before we change a line. Then we review the code and give you a written verdict — what to keep, fix, refactor or rewrite — and a fixed price for each module of the work. If the app is native, the plan includes moving it to Flutter: the Flutter core ships as an MVP while the native apps keep shipping. More on how it works: taking over an iOS or Android app.
Questions people ask
Will the app lose its reviews if it moves to my account? No. Both Apple and Google keep reviews and ratings with the app when it is transferred.
Can I publish an update without the old developer? Yes, once the app is in a developer account you control and, on Android, the signing question is settled. After that, updates no longer depend on the old developer.
How long does an app transfer take? On Google Play, support says it replies within two business days (as of October 2026). On the App Store, the transfer completes when your Account Holder accepts it; the preparation — TestFlight, App Groups, push keys — usually takes longer than the transfer itself.
Should we rewrite the app? Not by default. A review decides part by part whether to keep, fix, refactor or rewrite; rewrite only what is cheaper to replace than to fix, and keep what works.