Release notes written for each version update
Why it matters
Release notes reading "Bug fixes and improvements" signal abandonment to returning users and erode update-opt-in rates, which App Store Connect surfaces in your analytics and uses indirectly in ranking. Worse, release notes that describe features not present in the shipping build violate App Store Review Guideline 2.3.1 (Accurate Metadata) and can trigger rejection on a point release that would otherwise pass review.
Severity rationale
Low because generic release notes rarely cause rejection directly; impact is on retention and reviewer goodwill.
Remediation
Write release notes in user-facing language describing what actually changed: "Fixed crash when uploading images over 10 MB," "Added dark mode," "Sync is 40% faster." Keep it to 2-5 bullets. Store the file at fastlane/metadata/ios/<locale>/release_notes.txt and the matching fastlane/metadata/android/<locale>/changelogs/<versionCode>.txt so each submission ships with accurate, version-specific copy.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the App Store Metadata & Listing Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from app-store-metadata-listing·automated