Guideline 2.3.1

Guideline 2.3.1 - Accurate Metadata: Insufficient Review Notes for Major Update

Low SeverityEasy FixTypical Fix: 1-2 hours0 Reports

Also known as:Review notes do not provide sufficient detail about changesApp includes significant changes not explained in review notesNew features were not documented in the review notesMajor update requires detailed explanation of changesPlease provide more information about the changes in this update

Our Take

Apple is rejecting your app update because the review notes don't explain major changes in the new version. When you submit an update with significant new features, redesigned UI, or changed functionality, Apple expects detailed review notes explaining what changed and how to test the new features. This rejection is particularly common when: (1) the app's primary category or purpose has changed, (2) a major UI redesign makes the app look completely different from the previous version, (3) new IAP or subscription features have been added, or (4) new permissions are requested without explanation. Apple reviewers compare your new submission against the currently live version. If the delta is large and the review notes are generic ('Bug fixes and improvements'), they'll reject for insufficient information rather than spend time guessing what changed.

Resolution Guide

Write detailed review notes

For each major change, explain: what it is, why it was added, and how to test it. Include step-by-step instructions for reaching new features.

Highlight new permissions

If you added camera, location, microphone, or other permissions, explain exactly when and why they're requested.

Explain the redesign

If the UI changed significantly, describe the new navigation structure and key differences from the previous version.

Provide screenshots or video

For complex features, include a link to a short video walkthrough in the review notes. Use an unlisted YouTube link or Loom.

Update demo credentials

If the auth flow changed, provide fresh credentials and login instructions.

Prevention

Treat review notes as a change log for Apple, not for users

For major updates, include a section-by-section breakdown of changes

If your update touches IAP, permissions, or core navigation, always write detailed notes

Template your review notes: 'What Changed', 'How to Test', 'New Permissions', 'Known Issues'

Example Rejection Email

From:Apple App Review Team

Subject:Guideline 2.3.1 - Accurate Metadata: Insufficient Review N

Guideline 2.3.1 - Performance - Accurate Metadata Your app includes significant changes from the previous version, but the review notes do not provide sufficient detail about what has changed. Specifically, the app appears to have undergone a major redesign and includes new features that were not explained in the review notes. Next Steps: Please update the Review Notes in App Store Connect to include: - A detailed description of all changes made in this update - Instructions for accessing and testing new features - An explanation for any new permissions requested - Updated demo account credentials if the sign-in flow has changed

Before & After

Before — Rejected

Review Notes: 'Bug fixes and performance improvements.'

After — Approved

Review Notes: 'MAJOR CHANGES IN v3.0:\n1. Added video messaging (tap the camera icon in any chat thread)\n2. Redesigned home screen with new tab navigation\n3. Added premium subscription ($4.99/mo) -- accessible from Settings > Upgrade\n4. Now requests microphone permission for voice messages (triggered when user taps voice message button)\nDemo account: review@app.com / ReviewPass123'

What changed: Apple needs enough detail to plan their review. Generic notes for a major update guarantee a rejection.

Community Solutions · 0

More Guideline 2 (Performance) rejections

View all Guideline 2 rejections