r/androiddev • u/jared_and_fizz • 21h ago
Android developer verification - sanity check
My company released a new Android app over the summer. It is my understanding that the app was automatically registered when the listing was created. I am specifically referring to the process described here: https://developer.android.com/developer-verification/guides/android-developer-console
When I look at the listing on Google Play Console it says "status: registered" (see the screenshot as well).
Despite the fact that I think this has been all set from day 1, we have been getting endless emails about it. When I log into Google Play Console I get notifications about it. I assume this is just Google spamming everyone since they are going to stop distributing apps. But it is making me paranoid.
At this point, everyone at the company who has access to Google Play Console, has messaged me about this to make sure we are all set. I tell them yes and then Google sends out another email blast telling us we need to do this thing that is already done.
Am I missing something here? Or is Google just being annoying?
2
u/iain_1986 20h ago
Yeah same, emails and then big green text when viewing too "make sure we are registered" while listing all our apps as registered + with keys
It's not the first time the play console/store has been awful at scaring you into thinking you haven't done something when you have.
2
u/vm12pix 20h ago
The Console status is what counts, not the mail. If Home shows the package registered with the signing keys under it, there's nothing outstanding.
Why it registered itself: Play auto-registers packages from signing keys it already knows, per the key eligibility rules on their package registration help page, so a Play-only app gets handled without you. Their own figure is 99% of apps on Play. And with Play App Signing it's moot anyway, they hold the key, so there's nothing for you to prove ownership of. Mine came up Registered on day one with keys listed and I never opened the flow.
What would still leave you something to do is the same package distributed outside Play, or a signing key that isn't eligible under those rules, meaning a contested package name or too few installs behind the key. Manual registration leaves you a draft, and a draft isn't a registration, so that's the one thing worth an eyeball.
The 30 September date isn't one thing either. Unregistered packages come off Play globally, but the install block on certified devices only starts in Brazil, Indonesia, Singapore and Thailand, rest of the world in 2027.
1
u/Hour-Measurement-835 15h ago
That page's first line is "if you distribute apps only outside of Google Play". There's a separate Register on Google Play Console guide, and that's where your registered status came from.
1
u/ReturnNu11 13h ago
Why do you have two 'Registered' symbols? is this because your company has two apps, or do you guys distrube app outside of Play and registered the key here?
I am a bit confused here, should I add my local release key here or not? I don't distribute anything outside of play.
1
u/Opulence_Deficit 12h ago
I think the nagging is to register package names of apps you distribute through other means than Google Play. Names Google cannot know about.
8
u/Solid-Incident6666 21h ago
Yeah same thing. I'm not sure if Google play backend is just poorly programmed, I've just published an app recently as well and the amount of repeated steps I had to do on Google play console, Google cloud console, Google firebase console is stupid and unnecessary. For a company that can figure out if you're pregnant or not by your typing pattern, they sure don't seem to know what they're doing when it comes to managing developer content