Two ways to fail follow from binding a name to a key fingerprint [3]. Either the package name is not registered at all, or it is registered against a key other than the one that signed the artifact a tester just tapped. Teams that let each build machine mint its own debug keystore own the second failure and mostly do not know it yet. The dev.to writeup flags exactly this case: if the staging APK is signed by whichever laptop ran the last build, there is no stable key to register [14].
So count the applicationIds. The post's example team ships com.yourapp, com.yourapp.staging, com.yourapp.qa, and a .dev suffix on debug builds so testers can keep two versions side by side, and Android treats each as a distinct package [9]. Google's March 2026 sweep auto-registered names and signing keys for the large majority of apps already on Play [7]. Staging was never on Play [10]. Four names, one carried across, three to file by hand [1]. The app that gets argued about in planning is the one already handled.
The 95% figure deserves the usual treatment. It describes certified devices as a share of Android outside China [2], which is a claim about the global installed base, not about the phones in your QA drawer. The remaining 5% [2] is not allocated to you, and a retail handset held by a contract tester in Sao Paulo or Jakarta is certified. Plan as though the number is 100.
The exemptions hold where they are written and not one step further. adb install keeps working, and Google has said so plainly [5]. Apps pushed by an EMM Device Policy Controller, or published as private apps in Managed Google Play, are exempt indefinitely [6]. Neither one describes the actual path most builds take, which is a link in a chat message, tapped on a device that is sometimes the tester's own [15]. That path needs a registered package or the advanced flow Google shipped in August [8]. The author's prediction about where the friction lands is the believable part: it turns into "just test it on the emulator instead" [17].
The good engineering here is that the state is queryable. The Android Developer ID Status API reports whether a package name is already registered [11], which means a pipeline can assert registration for every flavor it builds instead of finding out at install time on someone else's phone. Adding names under an already-verified account is a form, not a negotiation, but it is a form nobody has filled in, and it has to be done before enforcement rather than after installs start failing [13].
One caveat on sourcing. This is a single developer's reading of the rules, written when enforcement was about a month out [16], and the same post advises confirming your own registration in the Play Console rather than assuming the March sweep covered you [18]. Global rollout follows in 2027 [12], so the four-country window is where the process gets debugged.
