If your app was rejected for having "Beta" in its name and the notice pointed at Guideline 2.3.10, the citation can be confusing, because the rule that most directly bans beta naming is actually Guideline 2.2. Either way the outcome is the same: words like Beta, Demo, Trial, and Test do not belong in an App Store listing, because the store is for finished products and your metadata has to be accurate. Here is which guideline applies, why Apple rejects this, and exactly where to scrub the wording.
Short answer
Yes, "Beta" in your app name or metadata will get the app rejected, because the App Store is for finished products, not pre-release versions. Guideline 2.2 states plainly that demos, betas, and trial versions of your app do not belong on the App Store and that you should use TestFlight instead, while Guideline 2.3.10 requires metadata to be accurate and free of irrelevant information, which reviewers sometimes cite for beta wording. The fix is to remove Beta, Demo, Trial, and Test from your name, subtitle, screenshots, and description, ship the finished app to the store, and run your actual beta through TestFlight.
What you should know
- Beta naming gets rejected: Beta, Demo, Trial, and Test do not belong in a listing.
- 2.2 is the core rule: betas belong on TestFlight, not the App Store.
- 2.3.10 is about metadata: accurate, relevant metadata, sometimes cited for this.
- It is not just the name: subtitle, screenshots, and description count too.
- TestFlight is the home for betas: that is where pre-release testing happens.
Which guideline actually applies?
Both can appear, for related reasons. Guideline 2.2, Beta Testing, is the most direct: it says demos, betas, and trial versions of your app do not belong on the App Store and directs you to TestFlight for pre-release builds. Guideline 2.3, Accurate Metadata, and its subsection 2.3.10 require that your metadata be accurate and focused on the app itself without irrelevant information, which a reviewer may invoke when "Beta" in the name suggests the listing is not a finished product. So if your rejection cited 2.3.10, read it alongside 2.2; the underlying message is that an App Store listing must present a final, shipping app, and beta wording contradicts that.
Why does Apple reject beta, demo, and trial naming?
Because the App Store is meant to distribute finished software, and that wording signals the opposite. A name like "MyApp Beta" tells users and the reviewer that the app is unfinished or experimental, which is exactly what TestFlight exists to handle, so putting it on the public store both misrepresents the app and bypasses the intended testing channel. The same logic covers Demo and Trial, which imply a limited or sample version rather than the real product. Apple wants the store to read as a catalog of complete apps, so it treats pre-release labeling as either inaccurate metadata or a misuse of the store for beta distribution, depending on how the reviewer frames it.
How do you fix it?
Remove the pre-release wording everywhere it appears, not just the name. The table lists the places to check.
| Where | What to remove |
|---|---|
| App name | Beta, Demo, Trial, Test, and similar labels |
| Subtitle | Any pre-release or "preview" wording |
| Screenshots | Captions or overlays that say beta or demo |
| Description and promo text | Statements that the app is a beta or trial |
After scrubbing those, submit the app as the finished product it is, and move your real beta testing to TestFlight, which is built for distributing pre-release builds to testers without putting them on the public store. If part of your app genuinely is a limited free tier, describe it as a free version with in-app purchases rather than a "trial," which is accurate and acceptable, instead of labeling the whole listing as pre-release.
What to watch out for
The first trap is removing "Beta" from the name but leaving it in a screenshot caption or the description, which still draws the rejection, so clear it from all metadata. The second is reading a 2.3.10 citation too narrowly and missing that 2.2 is the broader reason, which matters if you reply in Resolution Center. The third is shipping a genuinely unfinished app under a renamed title, since a beta-quality app can still be rejected for crashes or incompleteness under the performance guidelines even with clean wording. App naming and metadata are separate from your app's security, so they sit apart from a pre-submission scan such as PTKD.com (https://ptkd.com), which reads the binary against OWASP MASVS; the wording fix happens in App Store Connect.
What to take away
- "Beta" in your app name or metadata gets the app rejected; Beta, Demo, Trial, and Test do not belong in an App Store listing.
- Guideline 2.2 is the core rule, since betas belong on TestFlight, while 2.3.10 about accurate metadata is sometimes cited for the same wording.
- Remove the pre-release wording from the name, subtitle, screenshots, and description, then submit the finished app and run real betas through TestFlight.
- A limited free tier should be described as a free version with in-app purchases, not labeled a trial or beta across the listing.
