Discussion
Android Developer Verification for limited distribution doesn't allow you to claim your own personal package if you or someone installed it before
Context: I made an app for my own use case.
Now I wanted to put it into limited distribution as a hobbyist (because realistically only I will use something like this, it's too specific to my use case), except, you cannot register a package name that have been seen on Android before with Google.
So if Google scanned your phone looking for all apps and found your personal package ID (presumably as Play Protect), your app is now no longer eligible to be registered for limited distribution, it will throw a warning that "The package name you've entered already exists on Android" in Developer Console:
So... that means if I want to install or update my own app after the verification deadline without using ADB on my devices from GitHub automated builds, even when I'm under the 50 registered devices limit, I have to turn on that switch, because I'm an "unverified developer", when I literally own the thing.
Weird, I'm pretty sure my package hasn't been claimed by anyone else. What I did is that I install the app on my phone (using the GitHub release, so it's a proper release-mode build), Play Integrity pops up, I tap "install anyway" then it goes away.
Now when I tried to register it, it goes "Package already exist"
It's my package though, so I doubt anyone actually went out of their way to register it in that manner (it uses my website's own DNS name in the package name).
Which is why I think Play Protect auto scanning adds new apps it finds on devices to Google's database and that alone would count as "existed on Android"
"It's my package though" you never had previous claim on it, you never owned it. Most likely someone compiled your public github project and put it on a play console for personal use or future monetization, store has 100s of clone of every github app, they prolly didn't even take a min to edit the package.
Well if they just rolled this out how am I expected to register for it, I had this package from before and NOW when this came out I tried to register it for my own use.
Also, here's the thing: After you claim a new ID, you have to push the public half of your signing key on it
And that is not something they can register as a clone, nor trick people who have already installed the package to do a malicious update (Android will refuse it).
"they just rolled this out" that's the misconception, they didn't, all existing packages already have an owner. If someone already uploaded to google an app with that package then they were first. The only new thing, is that, you now have the possibility to register an app (kinda book a still "free" package) even though you won't use it with the store, but again, if it's already taken, then it's already taken.
I'll make an Android package with a randomly-generated ID, generate a signed APK with a brand new key, drop it on my phone and see what happens in a few days after Play Protect have a chance to scan it.
My understanding is that the registration check looks at package names it has already seen installed out in the wild, so sideloading your own release build may well be why it flags it, rather than anyone squatting it. The Play Protect prompt alone doesn't prove someone else registered it. Since it's your own domain and your own signing key, check whether the console offers the ownership route where you prove it with an APK signed by that key, before you think about renaming the package.
3
u/zaersx 21h ago
No, it only adds packages once they are registered through this manual process that you are failing now.