My App Developer Disappeared: How to Get Your App Back
Your developer stopped replying and holds your app. What to collect, how store transfers and signing keys work, and what to do if the code is gone.

It usually starts with a reply that takes a week, then two weeks, then none at all. Meanwhile your app needs an update, and you realise you don’t know where the code is or whose account the app is on.
It’s a stressful spot, but most of it can be untangled. Here’s the order I’d work in.
First, work out what you actually control
Make a list before contacting anyone else. For each item, write down who owns it and whether you can log in:
- Source code: GitHub, GitLab, Bitbucket, or only the developer’s laptop
- Apple Developer account: yours or theirs
- Google Play Console: yours or theirs
- Backend and database: Firebase, AWS, Azure, Supabase or a server
- Domain and DNS: often the thing that takes everything down when it lapses
- Email service, payment accounts, push notifications, maps and other API keys
- Android signing keys and iOS certificates
- Your contract, especially the part about who owns the code
Check your email for invitations and receipts. People often have more access than they think. If you paid for an Apple or Google account yourself, there’s a good chance you’re the owner.
Send one clear last request
Give the developer an easy way to finish well. A short, polite message with a specific list and a date works better than an angry one:
We’re moving maintenance of the app in-house. Could you please send the following by Friday the 14th: full source code, the Android upload keystore and passwords, and the store transfer? We’ll pay any reasonable invoice for your time.
Offering to pay for an hour or two is often the cheapest thing you’ll do in this whole process. Use every channel you have: email, phone, the freelance platform, and their company address. Keep a record of each attempt, because you may need it later.
If the app is on the developer’s account
Apple and Google both let an app move between accounts while keeping its reviews and users, but the current account holder has to take part.
- Apple: the sender starts the transfer in App Store Connect, and the Account Holder on your side accepts it. There are conditions to meet first, so check Apple’s current list.
- Google Play: a transfer request goes to Google, using identifiers from both accounts. Reports don’t move with the app, so export what you need.
If the developer won’t respond at all, contact Apple and Google support and explain the situation, with proof that you own the business and the app. Be realistic: stores are cautious about moving an app without the account holder’s consent, and it may take a formal legal request or may not work at all.
Signing keys
On Android, updates have to be signed with the right key. Whether a lost key is a disaster depends on how the app was set up:
- With Play App Signing, Google holds the app signing key. If the upload key is lost, the account owner can ask Google to reset it. This is the usual, recoverable case.
- Without it, the original key is the only key. If it’s gone, you can’t update that listing and will need a new one.
On iOS, certificates and provisioning profiles can be regenerated from the developer account, so if you control the account, this part is easy.
If you have no source code
This is the hardest case, and you deserve a straight answer. For a Flutter app, the release build contains compiled machine code and doesn’t include readable Dart, so you can’t practically recover the original project from the store download. Native apps are recoverable only in part, and the result isn’t something you’d want to maintain.
Your backend data, though, is usually what matters most. If you can get to the database and the design files, a rebuild is often faster than the original project was, because the product decisions are already made. Your existing app also works as a precise specification.
The legal side
Who owns the code depends on your contract and the law where you and the developer are. Don’t assume that paying for it means you own it. If there’s serious money involved, a short letter from a lawyer can get a response when your messages haven’t. If you hired through a platform like Upwork, check its terms and contact its support too. I’m a developer and this isn’t legal advice.
Keep the app alive meanwhile
- Renew the domain and any hosting that’s about to expire
- Add yourself as an owner everywhere you can
- Change passwords on accounts you control, and remove the developer’s access once you have what you need
- Check store deadlines, since an out-of-date app can become hidden from new users
Next time
Whoever you hire next, set things up so this can’t recur. Put the app on your own store accounts, keep the code in a repository you own, and store the keys somewhere you control. I’ve written a guide on what a proper handover should include, and if you’re picking up the pieces with a new developer, here’s how I stabilise an inherited codebase.
Takeaways
- List what you control before doing anything else.
- Send one clear request, and offer to pay for the handover.
- Moving a store listing needs the account holder’s cooperation.
- Lost Android upload keys are fixable under Play App Signing.
- Without source code, your data and your live app become the blueprint for a rebuild.
If you’re stuck in this situation, tell me what you’ve got access to, and I’ll tell you what’s recoverable.
Comments
Questions, corrections or your own experience — leave a comment below (GitHub sign-in).