Repository navigation
|
My app was flagged or rejected on App Store for this. Metadata promises features that do not ship in this build. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
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. 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 This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
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 tunedHow 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…