# Guideline 2.2 - Beta Testing: TestFlight-Quality App Submitted to App Store

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

Canonical URL: https://appstorereject.com/rejections/apple/2/guideline-22-beta-testing-testflight-quality-app-submitted-to-app-store

## Description

Apple is rejecting your app because it appears to be a beta, demo, or trial version rather than a finished product ready for public distribution. This covers apps that include 'beta' in the name or UI, apps that feel incomplete with limited functionality, and apps that explicitly time-gate features as a trial. This guideline exists because Apple positions TestFlight as the proper channel for beta testing and does not want the App Store to serve as a beta distribution platform. The rejection is usually triggered by: (1) the word 'beta' appearing anywhere in the app name, UI, or metadata, (2) features gated behind time-limited trials that aren't standard IAP subscriptions, (3) apps that feel like MVPs with very limited functionality, or (4) apps that prominently display build numbers, debug menus, or testing infrastructure. The fix depends on which trigger Apple identified. If it's the word 'beta,' that's a simple text change. If Apple thinks the app is too sparse, you need to either add functionality or better communicate the app's intended scope.

## Common variations

- App appears to be a beta version
- App includes the word 'Beta' in the name or UI
- App appears to be a demo or trial version
- App provides limited functionality that suggests it is not complete
- App contains debug or testing infrastructure visible to users

## Example rejection email

```
Guideline 2.2 - Performance - Beta Testing

Your app appears to be a beta version or contains references to being in beta. Specifically, the app includes the word 'Beta' in the app name and navigation bar.

Apps that are demos, betas, or trial versions are not appropriate for the App Store. Use TestFlight to distribute beta versions of your app.

Next Steps:
Please remove all references to beta testing from your app and metadata, and ensure the app provides a complete user experience.
```

## Resolution steps

## Quick Assessment
- **Risk level:** Low
- **Resolution path:** Fix & Resubmit
- **Typical turnaround:** 1-2 hours

## The Fix

1. **Remove all beta references** -- Search the entire codebase and all assets for 'beta', 'preview', 'early access', 'alpha', 'demo', and 'trial'. Remove them from: app name, navigation bars, splash screens, about screens, Info.plist display name, and App Store Connect metadata.

2. **Remove debug/testing UI** -- Hide or remove: build number displays, debug menus, log viewers, feature flags UI, developer settings, and any testing infrastructure visible to users.

3. **Remove time-based trials** -- If the app limits features after a time period (e.g., '14-day trial'), convert to a proper IAP or subscription model, or remove the restriction entirely for the free version.

4. **Ensure the app feels complete** -- Every screen should have real content, every button should work, and the core user journey should feel polished. If the app is intentionally minimal, add an onboarding flow that communicates the app's focused purpose.

5. **Update App Store metadata** -- Remove beta language from the description, What's New, and keywords. Don't mention upcoming features that aren't shipped yet.

## Prevention
- Use build configurations to strip all beta/debug UI from release builds automatically
- Never include 'beta' in your App Store listing even if you consider the product early-stage
- Use TestFlight for actual beta testing, not the App Store

## Appeal guidance

If the app is genuinely feature-complete and Apple is misreading its scope, explain in the Resolution Center what the app does and why the feature set is intentional. For utility apps with a single focused purpose, emphasize that simplicity is a design choice.

## Before / after examples

**Before:** App title: 'PhotoSync Beta' with a banner in the navigation bar reading 'BETA - Report bugs at beta@photosync.com'
**After:** App title: 'PhotoSync' with no beta references. Bug reporting moved to a 'Contact Support' option in Settings.
**Why it works:** Remove all beta language. Bug reporting is fine, but frame it as customer support, not beta feedback.

## Common questions

**Can you appeal a 2.2 rejection?**

If the app is genuinely feature-complete and Apple is misreading its scope, explain in the Resolution Center what the app does and why the feature set is intentional. For utility apps with a single focused purpose, emphasize that simplicity is a design choice.

**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-22-beta-testing-testflight-quality-app-submitted-to-app-store*