Before submission.
WHAT TO VERIFY IN THE BUILD
Release configuration, not debug Debugging and logging disabled or reduced Code shrinking and obfuscation enabled No test or placeholder content No development endpoints
WHAT TO CHECK
Version number and build number incremented Permissions limited to what is used Icons and launch screens present at every required size Signing configured correctly
WHAT SIGNING IS
Cryptographic proof the application came from you.
WHY IT MATTERS ENORMOUSLY
Losing your signing key on Android means you cannot update the application at all.
WHAT TO DO ABOUT THAT
Use the platform's key management, and back up your credentials securely.
WHAT TO TEST BEFORE SUBMITTING
The release build, on physical devices Upgrade from the previous version, with real data Every permission flow, including refusal Behaviour with no network
WHY THE RELEASE BUILD SPECIFICALLY
Shrinking and obfuscation can break reflection-based code, and this appears only in release.
WHAT TO PREPARE
Store listing content, screenshots, and privacy disclosures.
WHAT TO KEEP
The mapping file, for deobfuscating crash reports.
