Repository navigation
|
How can a team catch Play app package name not registered for developer verification automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rhoE 'applicationId[[:space:]=]+"[^"]+"' --include='*.gradle' --include='*.kts' . # then confirm each distributed package name is registered in Play Console developer verificationRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Every Play app package name must be registered in Play Console for Android developer verification by 30 September 2026. This leg is global. Unregistered apps risk global removal from Google Play. Detection is manual in Play Console. Development-build package names that are never distributed do not need registration. The fix. Open Play Console, complete developer verification, register every distributed package name, and re-check after adding a new applicationId or product flavor. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
GOOGLE-PLAY-APP-REGISTRATION-MISSINGwith a coverage line and a proper exit code.What the hit means. Every Play app package name must be registered in Play Console for Android developer verification by 3…