"Not registered" but it is: 4 real cases before the Sept 30 deadline

The September 30 deadline for Play package name registration is three days away. Most apps were registered automatically, and my earlier post covers how to check yours.

This post is about the other situation: Play Console says one thing, the release page says another, and you are not sure what to believe. These are four real cases I ran into in the last week, from the Play Help Community and from a client. Each one looked like a Google bug. Most of them were not.

Case 1: "Registered", but the package name is "already in use"

What they saw: A Flutter app. The package showed as registered under Android developer verification, but creating the app in Play Console failed with "already in use".

Why: The package name was com.example.hello_flutter. That is the Flutter template default. Thousands of projects ship with it, and Play does not accept apps under com.example at all.

Fix: Change the package name. If the app was never published, you lose nothing:

1. In android/app/build.gradle (or build.gradle.kts), change applicationId to something unique, like com.yourname.appname. namespace can stay as it is.
2. If you use Firebase, add a new Android app with the new package name and download the new google-services.json (or run flutterfire configure again). Your Firebase project and data stay the same.
3. Register the new name under Android developer verification, then create the app in Play Console with it.

After the first release the package name can never change, so pick one you are happy with.

Case 2: "No eligible signing keys are available"

What they saw: The developer had two certificates for the app. Neither one appeared as an option for registration.

Why: Eligibility is based on known installs per signing key. From Google's help page:

• A key with over 50% of known installs has priority.
• If no key passes 50%, every key with 50 or more installs is eligible.
• Under 50 installs, it is first come, first served.

This app was also preinstalled on a manufacturer's devices. That build can easily count for most of the installs. If the manufacturer signed it with their own key, the eligible key belongs to them, not to the developer.

Fix: Find out who holds the key used for the preinstalled build. Then open a case from the Help page inside Play Console with the package name, the SHA-256 fingerprints of both certificates, and a note that one build is a manufacturer preinstall. With the deadline this close, open the case today instead of waiting for forum replies.

Case 3: Registered, but the release is still blocked

What they saw: The package showed as registered, but the production release failed with an "unregistered package name" error.

This one I could not solve from the outside, but there are three things worth ruling out before your ticket sits in a support queue:

1. Same account. The package has to be registered in the same Play Console developer account that owns the app. Not in a separate Android Developer Console account, and not in another Play account.
2. Same key. Compare the certificate you registered with the app signing key under Test and release → App integrity. If you registered the wrong one (for example the upload key instead of the app signing key), Play may treat the release as coming from an unregistered key.
3. Fresh release. If you registered after creating the release draft, discard the draft and create a new release. An old draft does not always pick up the new state.

A related case from the same week: a developer who used Internal app sharing got the same kind of error. Internal app sharing builds are signed with a different key, and the fix was to register that key as an additional key for the package.

If all of this checks out, the problem is on Google's side. Open a case from the Help page inside Play Console and attach two screenshots: the one showing "Registered" and the release error.

Case 4: "My registration disappeared"

What they saw: A client of mine. We had checked her app together, confirmed it was registered and closed the order. Then she wrote back: "It says Package not registered."

Why: Nothing was wrong. On the Android developer verification page there is a filter menu, and one of the options is literally called "Package not registered". She was reading the filter's label as the status of her app.

How to actually check:

1. Select the "Package not registered" filter. If the list is empty (0 apps), you are fine.
2. Open Package names. The status column should say Registered.

I am including this case because it is the most common one, and it causes real panic three days before a deadline that says "removed from Play".

After September 30

Google's wording is clear: apps not registered by September 30 "will be removed from Play". Identity verification for installs outside Play also starts in Brazil, Indonesia, Singapore and Thailand on the same day, and goes global in 2027. So this topic is not going away.

Quick checklist

• [ ] Package name does not start with com.example
• [ ] Registered in the same account that owns the app
• [ ] Registered certificate matches the app signing key in App integrity
• [ ] Extra keys (Internal app sharing, builds outside Play) added
• [ ] New release created after registration
• [ ] "Package not registered" filter shows 0 apps

---

I fix Google Play problems for small teams and solo developers: developer verification, target API updates, rejected releases. If one of your apps is still flagged and you want it sorted before Wednesday, I do it as a fixed-price job: developer verification on Fiverr. I never need your keystore file.

Official sources:

• Registering Play package names (Play Console Help)
• Android developer verification (Android Developers)