Skip to content

App Store rejectionGuideline 2.3.12 - Performance - Accurate Metadata

Guideline 2.3.12 says an update’s What’s New text must clearly describe new features and product changes. Generic text like bug fixes is allowed only for simple bug fixes, security updates and performance improvements.

Short answer

Rewrite What’s New in this Version so it lists each significant change in plain words, for example new features, removed features, new prices or plans, and changed flows. Keep generic wording only for releases that really are just fixes. The field holds up to 4000 characters.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why Apple flagged the What’s New text, and the fix

  1. 01

    A feature release says only bug fixes

    “Apps must clearly describe new features and product changes in their “What’s New” text.” Apple, Guideline 2.3.12

    If the update adds or changes features, the What’s New text has to say so. List them one per line.

  2. 02

    Significant changes are left out

    “Simple bug fixes, security updates, and performance improvements may rely on a generic description, but more significant changes must be listed in the notes.” Apple, Guideline 2.3.12

    Apple allows a generic description only for simple bug fixes, security updates and performance improvements. More significant changes must be listed in the notes.

  3. 03

    Field limits and first versions

    “This property isn't available for the first version of the app but required for all subsequent versions.” Apple, Platform version information (What’s New in this Version)

    Also check: What’s New in this Version is limited to 4000 characters. It isn’t available for the first version of an app but is required for all later versions.

Checked against the vendor’s docs on : Apple: App Review Guidelines, 2.3 Accurate Metadata; App Store Connect Help: Platform version information; Apple: App Review (replying and appeals).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Resubmit before Apple’s holiday slowdown

Pay for the Diagnosis and send the rejection and access to the app by (US Eastern). The Diagnosis is back by . Pay for the Fix that day and it arrives as a pull request by , in time to build and resubmit before .

In past years Apple said reviews may take longer around the holidays: December 20 to 26 in 2024 (opens in a new tab), December 22 to 27 in 2023 (opens in a new tab), December 23 to 27 in 2022 (opens in a new tab). Apple hasn’t posted its 2026 dates yet (checked ). Approval stays Apple’s decision.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: App Store Guideline 2.3.1 Notes for Review · App Store Guideline 2.3 accurate metadata · App Store Guideline 2.3.7 keywords and name · App Store Guideline 2.3.3

Questions

More on this rejection

Should I reply to App Review or appeal?

Reply first. Apple says you can correspond with App Review in App Store Connect to resolve the issues before resubmitting, which is the place for a demo account, a screen recording or an explanation. Appeal to the App Review Board only if you believe App Review misunderstood the app or treated you unfairly. Apple allows one appeal per rejected submission and asks for specific reasons the app complies.

Is “bug fixes and performance improvements” ever enough?

Yes, when the release really is only simple bug fixes, security updates or performance improvements. Guideline 2.3.12 allows a generic description for those, but more significant changes must be listed.

Can you fix it for me?

Yes, through the App Fix Ticket: you send the rejection message and access to the app, Simon writes a diagnosis of what App Review hit and how to fix it, then fixes the code so you can resubmit. Each step has a fixed price, paid upfront. Approval stays Apple’s decision; the ticket covers the fix.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.