# Lost 16-year-old legacy signing key for a portfolio of 3 apps (23M total downloads). Is there any hope for a manual Play App Signing enrollment? — retained record

> Retained reddit record from reddit:androiddev.

Canonical: https://highsignal.app/data/records/61e149f8ff630eae

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:androiddev)  published 2026-10-21 01:47 ingested 2026-10-22 02:36

[original source ↗](https://www.reddit.com/r/androiddev/comments/1xbafzr/lost_16yearold_legacy_signing_key_for_a_portfolio/)

## retained text



```
Hey everyone,

I'm facing a massive issue with my dad’s old Google Play developer account and want to see if anyone here has gone through something similar.

Back around 2010, my dad had a freelancer build three Android apps that ended up getting 23 million downloads combined (the biggest one has 21M and 80k+ reviews). The last time they were updated was in 2015.

Recently, the apps got delisted because we didn't pass the new legacy account KYC yet (working on fixing that right now). But the real disaster is that the original developer lost the keystore file years ago. Because the apps are so old, they were never enrolled in Google Play App Signing.

I’m a developer myself now, and I want to completely rebuild his apps from scratch under the same package names, modernize them, etc.

Has anyone here ever lost an old legacy key on an account with millions of downloads? Were you able to get a human from Google support to manually enable Play App Signing for you, or is it completely hopeless and we have to start from zero with a new Package Name?

Would love to hear any stories or experiences. 

Thanks!
```



document fetched 2026-10-22 00:19 · canonical https://reddit.com/r/androiddev/comments/1xbafzr/lost_16yearold_legacy_signing_key_for_a_portfolio
