App Store RejectionGuideline 2.3.2 — Accurate Metadata — Beta Software

Apple Thinks You Submitted a Beta. Here's What to Clean Up.

Placeholder text, 'coming soon' screens, Lorem Ipsum, and test data are dead giveaways that your app isn't ready. Reviewers are instructed to reject anything that doesn't feel production-ready.

What Apple said

“Your app includes content or features that appear to be in a beta or test phase. Specifically, we noticed placeholder text, 'coming soon' labels, and features that are non-functional. Apps must be complete and ready for customers when submitted.”

What this actually means

Apple expects every submitted app to be the version you'd be comfortable shipping to paying customers today. Anything that signals 'still in progress' — placeholder copy, disabled buttons, hardcoded test emails, empty screens — will trigger this rejection. It's not about your app being imperfect; it's about it not looking finished.

What Apple needs to see

All visible text replaced with real, final copy — no Lorem Ipsum or 'TBD' anywhere in the UI
Every navigation item and button either functional or removed entirely from the build
Any 'coming soon' features hidden behind a feature flag or removed from this submission
Real or realistic sample data instead of obviously fake test content like 'user@test.com'

1Audit every screen in your app specifically looking for placeholder text, empty states, and disabled features
2Remove or hide any features that aren't complete using build flags — don't ship half-built UI
3Replace all test data with realistic dummy content that reflects how the app looks for real users
4Check your onboarding flow end-to-end — placeholder copy here is especially visible to reviewers
5Review your support page at yourapp.baseterms.com/support to ensure it's live and doesn't have any placeholder content either

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Support Page

Data Deletion Page

Generate my compliance pages — FREE

Common questions

Can I submit with some features locked or unavailable?

Yes — features that require server-side infrastructure or future content are fine, as long as the app handles the empty state gracefully. What you can't do is show a broken UI or a screen that says 'coming soon.' Either make it work or hide it.

I have a 'roadmap' screen in my app showing future features — is that okay?

Roadmap screens are fine if they're clearly presented as such and don't suggest that core functionality is missing. The problem is when upcoming features are presented as part of the current app experience but don't work.

My app uses 'beta' in its name — will that cause problems?

Using 'beta' in your app's name or description is a red flag and will likely trigger this guideline. Rename the app and remove beta language from all metadata before submitting to the App Store.