Skip to content
Discussion options

You must be logged in to vote

Guideline. 2.3.1 (App Store)

Severity in the playbook. medium

What triggers it. Listing or in app copy uses coming soon, beta, or a promised feature not present in the build. Mirrors the fastlane precheck future_functionality rule.

What to search your code for. coming soon, coming-soon, beta, will be available, in a future update, stay tuned

How to fix it. Describe only what the build does today. Remove coming soon and future feature promises from the listing.

The guard reports this as APPLE-2.3-FUTURE-FUNCTIONALITY. The full pattern is in data/rejection-patterns.json.


This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Pl…

Replies: 1 comment

Comment options

mjmirza
Nov 5, 2026
Maintainer Author

You must be logged in to vote
0 replies
Answer selected by mjmirza
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant