# Guideline 2.2 - Performance - Beta Testing
> Apple rejected the app under 2.2 because it looks like a demo, beta or trial. Ship the finished app to the App Store and run betas in TestFlight.
Canonical: https://app369.com/fix/app-store-guideline-2-2-beta-testing/
Last updated: 2026-11-10
Guideline 2.2 says demos, betas and trial versions of an app don’t belong on the App Store, and that beta builds go through TestFlight instead. A build or listing that presents itself as a demo, beta or trial can draw this rejection.
**Short answer**
Remove beta, demo and trial wording from the app and its metadata, and submit the version you want the public to use. Keep testing in TestFlight: up to 100 internal testers and up to 10,000 external testers, with each build testable for up to 90 days. Never pay testers or offer TestFlight access as a crowdfunding reward.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **Why Apple flagged the build as a beta, and the fix**
1. 01 ### **The app or its metadata says beta, demo or trial**
> “Demos, betas, and trial versions of your app don’t belong on the App Store” [**Apple, Guideline 2.2**](https://developer.apple.com/app-store/review/guidelines/#2.2) A name, subtitle, screenshot or in-app banner that says beta or demo can tell the reviewer the build is not the real product. Remove the label and submit the version you intend to release.
2. 02 ### **A test build was submitted instead of TestFlight**
> “Any app submitted for beta distribution via TestFlight should be intended for public distribution and should comply with the App Review Guidelines.” [**Apple, Guideline 2.2**](https://developer.apple.com/app-store/review/guidelines/#2.2) Builds meant for testers go to TestFlight, not to App Store review for release. TestFlight builds still have to follow the guidelines and be meant for public release later.
3. 03 ### **Testers are paid or rewarded for access**
> “apps using TestFlight cannot be distributed to testers in exchange for compensation of any kind, including as a reward for crowd-sourced funding.” [**Apple, Guideline 2.2**](https://developer.apple.com/app-store/review/guidelines/#2.2) Giving TestFlight access as a perk for backers, or paying people to test, breaks 2.2. Offer beta access for free and keep backer rewards separate from the beta.
4. 04 ### **A big beta update skipped TestFlight review**
> “Significant updates to your beta build should be submitted to TestFlight App Review before being distributed to your testers.” [**Apple, Guideline 2.2**](https://developer.apple.com/app-store/review/guidelines/#2.2) Also check: when a beta build changes a lot, send it to TestFlight App Review before testers get it.
Checked against the vendor’s docs on November 10, 2026: [Apple: App Review Guidelines, 2.2 Beta Testing](https://developer.apple.com/app-store/review/guidelines/#2.2); [App Store Connect Help: TestFlight overview](https://developer.apple.com/help/app-store-connect/test-a-beta-version/testflight-overview/); [Apple: App Review (replying and appeals)](https://developer.apple.com/distribute/app-review/).
## **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 Monday, December 7 (US Eastern). The Diagnosis is back by Thursday, December 10. Pay for the Fix that day and it arrives as a pull request by Thursday, December 17, in time to build and resubmit before December 20.
In past years Apple said reviews may take longer around the holidays: [December 20 to 26 in 2024 (opens in a new tab)](https://developer.apple.com/news/?id=iwvebnw2), [December 22 to 27 in 2023 (opens in a new tab)](https://developer.apple.com/news/?id=uijoypq9), [December 23 to 27 in 2022 (opens in a new tab)](https://developer.apple.com/news/?id=xpkhwg3l). Apple hasn’t posted its 2026 dates yet (checked October 30). Approval stays Apple’s decision.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**App Store Guideline 2.1 app completeness**](https://app369.com/fix/app-store-guideline-2-1-app-completeness/) · [**App Store Guideline 2.3 accurate metadata**](https://app369.com/fix/app-store-guideline-2-3-accurate-metadata/) · [**App Store Guideline 4.2 minimum functionality**](https://app369.com/fix/app-store-guideline-4-2-minimum-functionality/) · [**App Store Guideline 2.3.3**](https://app369.com/fix/app-store-guideline-2-3-3-screenshots/)
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.
**How many people can test a build in TestFlight? **+
Up to 100 internal testers from the App Store Connect team and up to 10,000 external testers. Each build can be tested for up to 90 days, and the first build added to an external group goes to App Review.
**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.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)