Update notes need to genuinely reflect the changes in the build — generic "bug fixes and improvements" text on a version with major new functionality, or listing features that aren't actually included in the update, both violate this.
Why apps actually get flagged
Usually a low-severity but real trigger when release notes are copy-pasted across versions without being updated to match the actual changelog.
A real example
"The 'What's New' text for your app update does not accurately describe the changes included in this version, per guideline 2.3.12."
The short version, in more detail
Guideline 2.3.12 asks that the What's New text describe what actually changed in a version. Notes that say only bug fixes and improvements on a release with major new functionality, or that mention features not included, misrepresent the update. It is usually a minor issue, but it is a real one that reviewers cite.
What this guideline covers
The release notes shown for each version in the listing.
Whether the notes reflect the real changes in the build.
Notes that list features not included in the update.
Copy-and-paste notes reused across versions.
What usually triggers this rejection
Generic text on a version that adds major features.
Release notes listing a feature that was cut from the build.
Identical text copied across many versions.
Notes that conceal significant changes such as a new payment model.
Marketing claims in the notes that are not true of the update.
How reviewers evaluate it
Reviewers compare the notes with changes they can see in the build.
They are more sensitive when a notable change is not mentioned.
They may check consistency with the review notes.
It is often caught alongside other metadata checks.
Common misunderstandings
Short notes are acceptable when the changes are small. The issue is accuracy.
The notes are not only for marketing. They are part of what is reviewed.
A rejection here usually concerns metadata, not the code.
Common questions
Is "bug fixes and improvements" always rejected?
Not always. It becomes a problem when it hides significant changes.
Do notes have to be long?
No. They have to be accurate for the version.
Can notes be changed without a new build?
Release notes are metadata and can be edited, but each version has its own notes.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.