Repository navigation
|
My app was flagged or rejected on App Store and Google Play for this. Metadata field overflow or banned decoration. 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. Apple 2.3.7, Google Store Listing (App Store and Google Play) Severity in the playbook. medium What triggers it. App name over the limit (Apple 30, Google 30), emoji in the title, all caps, or ranking and price claims such as number one, best, top, or free in the title or icon. How to fix it. Keep each metadata field within its limit and remove emoji, all caps, and ranking or price claims from the title and icon. 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. Apple 2.3.7, Google Store Listing (App Store and Google Play)
Severity in the playbook. medium
What triggers it. App name over the limit (Apple 30, Google 30), emoji in the title, all caps, or ranking and price claims such as number one, best, top, or free in the title or icon.
How to fix it. Keep each metadata field within its limit and remove emoji, all caps, and ranking or price claims from the title and icon.
The guard reports this as
BOTH-METADATA-DECORATION. 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 Play review. Run
bash scripts/install.sh install