A release checklist for AIR mobile apps
Most rejected or delayed releases come from small omissions. Print this list and tick it off before every build you plan to submit.
Identity and signing
- The application ID in the descriptor matches the ID registered in the store console.
- Your signing certificate and provisioning profile are valid for at least the next few months. Put the expiry dates in your calendar.
- You know where the certificate backup lives and who has the password.
Versioning
- Increase the version number in the descriptor. Stores reject a build that repeats a previous one.
- Keep the user-facing version label and the internal version number clearly separate in your notes.
Assets and permissions
- Every required icon size is present and none is upscaled from a smaller image.
- Splash and launch images exist for the device sizes you support.
- The permissions list contains only what the app uses. Remove anything left over from experiments.
Testing
- Install the exact release package on a real phone and a real tablet, not only a debug build.
- Test a fresh install, an update over the previous version, and airplane mode.
- Rotate the device during loading and during a dialog.
Store listing
- Screenshots show the current interface.
- The privacy statement covers every network call and every stored item.
- Release notes say what changed in words a user would use.