Do I need to register my app package in Play Console first?

Do I need to register my app package in Play Console before I can keep distributing to testers

No, not to keep distributing existing test builds to testers. Google Play’s testing docs say internal testing can start before an app is fully set up, closed testing only requires that setup be finished, and package registration is a separate developer-verification step. If you already have a test track working, package registration is not the thing that keeps your testers receiving builds.

The part people get wrong is mixing up three different things: creating an app in Play Console, setting up a testing track, and registering the package name. Play Console lets you create internal and closed tests for distribution, while package registration is part of Android developer verification. Those steps overlap in the same account, but they are not the same requirement.

If your goal is only to keep sending builds to testers already enrolled in your track, the practical answer is to stay on the track you already have and keep uploading releases there. Google Play says internal testing can be used even before an app is fully configured, and it supports up to 100 testers. Closed testing is the wider test track, and Google Play says testers in that track receive updates for the test version assigned to them.

Package registration becomes relevant when you are working through Android developer verification requirements or setting up a new package name. Google’s package-name registration help page says developers with a Google Play Console account must register package names to comply with those verification requirements, and it notes that Google will attempt to auto-register some apps. That is a compliance step, not the same thing as the day-to-day act of distributing a test release.

What actually blocks tester distribution is usually something simpler: the track is not set up, the tester list is wrong, the release is not rolled out to the track, or the tester never opted in. Google Play’s testing guide says closed testing uses email lists or Google Groups, and testers join through the opt-in link. If the tester is not on the list or has not opted in, they will not receive the test version, even if the package name is already registered.

The inconvenient part is that registration alone does not deliver a build to anyone. A package name can be registered and still have no active testers, no uploaded release, or no opt-in link shared. The distribution path still depends on the track, the tester list, and the release state in Play Console. If a tester says they cannot install your app, the first thing to check is the testing track, not the package registration page.

For new personal developer accounts created after November 13, 2023, Google Play adds a separate closed-testing requirement before production access: at least 12 opted-in testers for 14 continuous days. That rule affects production access, not whether you can continue a test track you already use. Google Play also says internal testing does not count toward that closed-testing requirement.

A concrete example helps. If you already have a closed test running and your testers are getting updates, you can keep uploading new closed-test releases while you finish package registration work in parallel. If you are starting from scratch with a new app and a new package name, you should create the app, set up the track, and complete the registration steps that apply to your account before you expect production access. Those are separate milestones.

If you use DevConnect, the same rule applies on the platform side, the test exchange still depends on your own Play Console setup, not on a shortcut around Google Play requirements. The platform can help you coordinate testers, but it does not replace package registration or Play Console track setup.

The shortest useful checklist is this: keep the existing testing track alive, confirm the tester list and opt-in link, upload the new release to that track, and complete package registration when the Play Console verification flow asks for it. That order keeps distribution moving without treating registration as the gate for every test build.