Guideline 2.2
Guideline 2.2 - Beta Testing: TestFlight-Quality App Submitted to App Store
Our Take
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.
Resolution Guide
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.
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.
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.
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.
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
Example Rejection Email
Consider Appealing
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
App title: 'PhotoSync Beta' with a banner in the navigation bar reading 'BETA - Report bugs at beta@photosync.com'
App title: 'PhotoSync' with no beta references. Bug reporting moved to a 'Contact Support' option in Settings.
What changed: Remove all beta language. Bug reporting is fine, but frame it as customer support, not beta feedback.
Community Solutions · 0
Sign in to share your solution.
More Guideline 2 (Performance) rejections
- Guideline 2.1 - App Completeness: App Crashes During Review
- Guideline 2.1 - App Completeness: App Requires External Hardware Not Provided for Review
- Guideline 2.1 - App Completeness: Crashes on Launch
- Guideline 2.1 - App Completeness: Demo Account Not Working
- Guideline 2.1 - App Completeness: IAP Products Not Found in Binary
- Guideline 2.1 - App Completeness: Missing App Icon