# Guideline 2.3.12 - Accurate Metadata: Major Feature Shipped as 'Bug Fixes' Update

**Guideline:** 2.3.12 · **Store:** Apple App Store · **Severity:** low · **Fix difficulty:** easy · **Typical turnaround:** 1-2 hours

Canonical URL: https://appstorereject.com/rejections/apple/2/guideline-2312-accurate-metadata-major-feature-shipped-as-bug-fixes-update

## Description

Apple is rejecting your app update because significant new features or functionality were added, but the What's New text only mentions 'Bug fixes' or 'Performance improvements'. Apple requires that the What's New section accurately describe changes users will notice, especially new features that change the app's behavior or add capabilities. This guideline was added because developers were using vague release notes to slip major changes past review. Apple wants users to know what's changing in each update, and they also use the What's New text to focus their own review efforts. If you ship a completely redesigned home screen but write 'Bug fixes,' the reviewer has to discover the changes on their own, which wastes their time and triggers suspicion. The rejection is typically triggered when: (1) the binary diff shows major changes but the What's New is minimal, (2) the reviewer discovers undocumented features during testing, or (3) the app's behavior differs significantly from the previous version without explanation.

## Common variations

- What's New text does not adequately describe changes in this update
- Significant features added without documentation in What's New
- Release notes do not reflect major changes to app functionality
- What's New text is generic and does not describe actual changes

## Example rejection email

```
Guideline 2.3.12 - Performance - Accurate Metadata

Your app's What's New text does not adequately describe the changes in this update. Specifically, the What's New text states 'Bug fixes and performance improvements,' but the update includes significant new features and changes to the app's functionality.

Next Steps:
Please update the What's New text to accurately describe the changes in this version, including any new features, significant UI changes, or changes to existing functionality.
```

## Resolution steps

## Quick Assessment
- **Risk level:** Low
- **Resolution path:** Update What's New text in App Store Connect (no new binary needed)
- **Typical turnaround:** 1-2 hours

## The Fix

1. **List all user-facing changes** -- Go through your commit history or release notes and identify every change a user would notice: new features, UI changes, behavior changes, new permissions, new IAP.

2. **Write descriptive What's New text** -- Use bullet points or short paragraphs to describe each significant change. Lead with the biggest changes.

3. **Be specific** -- Instead of 'Performance improvements', write 'Reduced app launch time by 40%' or 'Fixed a crash when opening large files.' Users and Apple both appreciate specificity.

4. **Update review notes too** -- If you have major changes, update the Review Notes field with testing instructions for the new features.

5. **Keep bug fixes too** -- You can still mention bug fixes, but they shouldn't be the only thing listed when there are major new features.

## Prevention
- Maintain a running changelog during development
- Write What's New text as part of the release process, not as an afterthought
- Follow a template: New Features > Improvements > Bug Fixes
- If the update is truly just bug fixes, that's fine -- but be specific about which bugs were fixed

## Before / after examples

**Before:** What's New: 'Bug fixes and performance improvements.'
**After:** What's New: 'New in v4.0:\n- Dark mode support across all screens\n- Redesigned home feed with personalized recommendations\n- Added video messaging in chats\n- New subscription tier: Premium Plus ($9.99/mo)\n\nBug Fixes:\n- Fixed crash when uploading images over 10MB\n- Fixed notification badge count not clearing'
**Why it works:** Every significant user-facing change belongs in What's New. Be specific about both features and fixes.

## Common questions

**How long does this typically take to fix?**

Typical turnaround is 1-2 hours (difficulty: easy). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-2312-accurate-metadata-major-feature-shipped-as-bug-fixes-update*