skills.rest
cruisediary
cruisediaryCOMMUNITY
Explore all skills by this author →
GitHub

app-name-compliance

Detect App Store display-name violations in iOS/macOS project files.

13|1|Updated Mar 29, 2026
Search Tags:#compliance#info-plist#app-name#display-name#cfbundledisplayname#guideline-2-3-7#apple-trademarks
One-click install
npx skills add https://github.com/cruisediary/apple-app-review-skills --skill app-name-compliance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-name-compliance
Source: https://github.com/cruisediary/apple-app-review-skills/tree/main/skills/metadata/app-name-compliance
Command: npx skills add https://github.com/cruisediary/apple-app-review-skills --skill app-name-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents App Store rejection by identifying display-name violations such as excessive length, beta/alpha labels, Apple trademark terms, and embedded version numbers in CFBundleDisplayName.

Core Features & Use Cases

  • Validates CFBundleDisplayName length against the 30-character limit for store display names.
  • Detects beta/alpha/test/demo terms in the display name.
  • Detects Apple trademark terms in the display name without explicit permission.
  • Detects version number suffixes like "App 2" or "MyApp v2" in the display name.
  • Produces actionable remediation guidance with file paths to fix issues before submission.

Quick Start

Run this skill against your iOS/macOS project to validate the app display name.

Frequently Asked Questions about app-name-compliance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my CFBundleDisplayName for App Store rejection risks?▼

To check your CFBundleDisplayName for App Store rejection risks, validate the display name length against the 30-character limit and detect beta, alpha, or demo terms that violate store guidelines.

Why does Guideline 2.3.7 reject my app display name?▼

Guideline 2.3.7 rejects app display names containing unauthorized Apple trademark terms, beta or alpha test labels, embedded version suffixes like App 2, or names exceeding the 30-character store display limit.

Does my iOS project display name allow beta or demo terms?▼

iOS project display names must not include beta, demo, alpha, or test terms. Scanning your Infos.plist and project files detects these labels and provides actionable remediation guidance to ensure compliance.

What is the maximum allowed length for an iOS app display name in the App Store?▼

The maximum allowed length for an iOS app display name in the App Store is 30 characters. Validating your CFBundleDisplayName metadata ensures it meets this limit before submission to prevent rejection.

Can I include version numbers like v2 in my CFBundleDisplayName metadata?▼

You cannot include version number suffixes like v2 or App 2 in your CFBundleDisplayName metadata. Detecting these embedded version numbers in project files helps prevent App Store submission rejections.

How to fix Apple trademark violations in my app display name?▼

To fix Apple trademark violations in your app display name, identify unauthorized trademark terms in your CFBundleDisplayName and apply the suggested remediations with specific file paths to rename the metadata.

Related Skills

Explore More Legal & Compliance Skills→
gsmlg-appgsmlg-app
2

project-metadata

Update application name, bundle identifier, and company details across Flutter platform configuration files.

Official
Intermediate
blitzdotdevblitzdotdev
14

reviewer

Inspect Xcode projects against 100+ App Store Review Guidelines.

Official
Advanced
OMIXECOMIXEC
1

app-store-preflight-skills

Scan Xcode projects for App Store submission risks and generate remediation plans.

Community
Intermediate
femitzfemitz

app-store-review

Identify and mitigate App Store rejection risks before submission.

Community
Intermediate