App Store 2.3.12 rejection: What's New release notes
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad app updates with missing or vague descriptions of substantive changes.
“Bug fixes and improvements” can be accurate, but it doesn’t describe a new payment model or a major feature. Under 2.3.12, Apple expects What’s New to explain significant changes. Generic wording is allowed for straightforward fixes, security updates, and performance work.
Compare the notes with the actual update
Review the changes users will notice: features, account behavior, purchases, and important workflow changes. We’d ask the person preparing the release to compare the notes with the finished build, not only a development ticket list.
Describe the changes plainly
Name the new capability and where users find it. Explain a changed behavior that could surprise an existing user. Keep private technical details and internal task numbers out of public notes.
Also update Notes for Review when the reviewer needs specific access or test instructions; that field has a different audience.
Read each localization and check that the notes describe this release. Tell Apple which text was updated. If the update genuinely contains only fixes, explain that accurately instead of inventing a feature announcement.
Messages this guide can help with
App Store 2.3.12 rejection; app store 2.3.12 denial; Guideline 2.3.12; What's New release notes
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 2.3.12 Checked 22 September 2026