If your AI-coded app came back from App Review with a Guideline 5.2.2 citation pointed at your icon, the reviewer is telling you the asset looks like it borrows protected third-party content. The headline guideline is about third-party services, not icons, which makes the rejection notice confusing to read. The trigger sits in a different part of the guidelines, and the fix turns on one detail.
Short answer
Guideline 5.2.2 (Third-Party Sites/Services) covers any app that uses, accesses, monetizes, or displays content from a third party. Reviewers cite it when an AI-coded app ships an icon that resembles a registered logo, character, or brand mark, even though 5.2.1 (Generally, Intellectual Property) or 4.1(c) (Copycats) is often the closer rule. The fix is to replace the icon with a fully original asset or provide written authorization. Apple requires that authorization on request, so a fair-use claim rarely clears the rejection on the first round.
What you should know
- 5.2.2 sits inside section 5.2 (Legal: Intellectual Property). It targets unauthorized use of third-party content, including content rendered into your icon, splash screen, or onboarding art.
- AI image generators create the most common trigger today. Models trained on web images often emit recognizable logos, characters, or trade dress without the user asking for them by name.
- The closer rule is often 5.2.1 or 4.1(c). Reviewers sometimes cite 5.2.2 because it carries the "authorization must be provided upon request" clause that lets them push the burden onto the developer.
- Authorization is the universal escape hatch. Either remove the protected element or upload a signed license from the rights holder.
- Apple updated 4.1(c) in November 2025. The current text explicitly forbids using another developer's icon, brand, or product name in your app's icon or name, without approval.
- Icon resemblance does not require pixel match. Trade dress claims cover color schemes, silhouettes, and characters drawn in a different style but recognizable as the same property.
What does Guideline 5.2.2 actually say in 2026?
According to Apple's App Review Guidelines section 5.2.2 (Third-Party Sites/Services), if your app uses, accesses, monetizes access to, or displays content from a third-party service, you must be specifically permitted to do so under that service's terms of use. The guideline ends with the sentence that drives most rejection patterns: authorization must be provided upon request.
The rule sits inside section 5.2 (Legal, Intellectual Property), next to 5.2.1 (Generally), 5.2.3 (Audio/Video Downloading), 5.2.4 (Apple Endorsements), and 5.2.5 (Apple Products). When an icon or in-app asset borrows third-party intellectual property, the technically closer guideline is 5.2.1, which forbids using protected trademarks, copyrighted works, or patented ideas in your app without permission. Reviewers often cite 5.2.2 anyway because it gives them a documented way to ask for authorization papers, while 5.2.1 reads as a flat ban with no clear escape route.
The distinction matters when you write your Resolution Center reply. A 5.2.1 reply is about ownership. A 5.2.2 reply is about authorization documents. Reviewers will read both kinds of evidence, but framing the answer the same way the guideline frames the question shortens the round-trip by one cycle.
Why does Apple cite 5.2.2 for AI-generated icons?
AI image generators trained on large web crawls have seen millions of registered logos, animated characters, sports league badges, and branded mascots. When a developer asks Replit Agent, DALL-E, Adobe Firefly, or Stable Diffusion for an icon described as "cute red plumber game character" or "fast blue hedgehog mascot", the model often emits an asset that resembles a recognizable property in style, color palette, and silhouette. Reviewers see the icon in the binary, recognize the trade dress, and pull the 5.2.2 lever because it is the cleanest guideline for asking the developer to prove authorization.
The Apple Developer Forums thread on Guideline 5.2.2 shows the same pattern repeated across years: a developer ships content that touches a third-party property, the reviewer asks for authorization documents, and the developer either produces them or removes the element. AI-generated icons are the modern version of the same story, with the difference that the developer did not consciously choose to copy.
The November 2025 update reported by 9to5Mac tightened the icon-specific rule by adding the line under 4.1(c) that forbids using another developer's icon, brand, or product name in your app's icon or name without approval. Reviewers now combine 4.1(c) with 5.2.2 on the same rejection notice, especially for icons that mix two recognizable brands or that borrow a known character.
Which third-party marks trigger the rejection most often?
Reviewers respond strongest to recognizable characters and registered logos. The table below maps the asset families that show up most frequently in AI-generated icon rejections.
| Asset family | Why AI generators often produce it | 5.2.2 risk |
|---|---|---|
| Game character mascots (Mario, Sonic, Pikachu) | Heavy presence in training data, emitted from generic prompts | High |
| Disney and Pixar characters | Strong visual signature, surfaced by style words like "Pixar style" | High |
| Sports league logos and team badges | Color and shape primitives encode the marks even in abstracted form | High |
| Streaming and social platform marks | Color schemes alone (Spotify green, X black) can trigger trade dress claims | Medium |
| Generic device silhouettes (iPhone, MacBook) | Falls under 5.2.5 (Apple Products), not 5.2.2 | Out of scope |
| Public domain emblems (historical seals, state flags) | Generally safe but watch for modern derivatives | Low |
The honest answer is that an AI-generated icon that pulls visual cues from Nintendo, Disney, Pokémon, Marvel, the NFL, or the major streaming brands is almost always going to draw a 5.2.2 (or paired 4.1) flag, even with the brand name omitted from the App Store Connect metadata.
How do I tell if my icon is in the danger zone?
Three checks catch most of the icons that get pulled.
The first check is reverse image search. Drop the icon into Google Lens, TinEye, or Yandex Images. If the top matches return registered logos, copyrighted characters, or branded merchandise, App Review will see the same matches.
The second check is trademark search. Run the name and the visual descriptor through the USPTO Trademark Search and the EUIPO eSearch databases. A mark in a related class is enough to trigger the rule, even if you operate in a different country.
The third check is a human read by someone outside the project. Show the icon to three people who did not work on the app and ask them to name the first brand or character it reminds them of. If two of them name the same protected property, the icon will fail review.
For builders shipping AI-coded or no-code apps where the icon is produced by a model and the binary is hard to audit by eye, a pre-submission scan against OWASP MASVS on the compiled IPA or AAB catches several adjacent issues at the same time, including hardcoded brand assets bundled inside resource folders. PTKD.com (https://ptkd.com) is one of the platforms focused on that kind of pre-submission read for iOS and Android builds.
What is the clean fix that clears 5.2.2 on the second submission?
The fix has three parts: replace the asset, refresh the metadata, and write the Resolution Center reply in the same shape as the guideline.
Replace the asset. Regenerate the icon with prompts that name the visual primitives you want (color, geometric shape, abstract motif) and avoid words that pull the model toward a known property (mascot, hero, character, style of X). If you keep an iconic design choice such as a specific color and shape combination, run the result back through the three checks above. Hand-illustration by a designer who has not seen the original AI output is the most reliable path.
Refresh the metadata. Apple's review covers the icon, the screenshots, the preview videos, the keywords, the app name, and the subtitle. Any of those that still echo the protected property will pull the rejection back. The Apple Trademark and Copyright Guidelines for third parties cover Apple's own marks; for other companies, check their brand pages or assume the use is not authorized.
Write the Resolution Center reply in the same shape as the guideline. State explicitly that the icon and all in-app assets are now original work, name who created them, and confirm that the app does not display or monetize third-party content covered by 5.2.2. If you have written authorization, attach the document (a PDF on the rights holder's letterhead is the format Apple accepts). The Apple Developer Forums thread on 5.2.2 shows that uploading authorization upfront, rather than waiting for the second request, shortens the cycle by one round.
What to watch out for
- A fair-use claim does not clear 5.2.2. Apple's reviewers do not adjudicate fair use; they require authorization on request.
- Removing the icon from metadata is not enough. The binary still ships the asset, and review tooling unpacks the IPA and inspects every PNG inside.
- Color palette alone can carry trade dress. A red square icon with a curved white check on it will read as one specific delivery brand even without the name.
- Sports team and league marks are aggressively defended. Even fan-made icons referencing the NFL, NBA, or Premier League draw a 5.2.2 flag.
- Apple Endorsements (5.2.4) is a separate trap. Icons that mimic the Apple logo or imply Apple ownership fall under 5.2.4 or 5.2.5, not 5.2.2.
- The myth that AI output is automatically original work. AI-generated images can still infringe; the prompt does not insulate the output from trademark or copyright claims.
Key takeaways
- Guideline 5.2.2 is the third-party content rule inside section 5.2 (Legal, Intellectual Property), and reviewers use it for AI-generated icons because it carries the "authorization on request" clause.
- The technically closer rules are 5.2.1 (Generally) and 4.1(c) (Copycats). Apple's November 2025 4.1(c) update added the explicit ban on using another developer's icon, brand, or product name in your app's icon or name without approval.
- The first-round fix is to replace the icon with a fully original asset, refresh every metadata field that echoes the protected property, and answer the Resolution Center in the same shape as the guideline.
- Three checks (reverse image search, trademark database search, three-person blind recognition test) catch most AI-generated icons that are headed for a 5.2.2 rejection.
- For teams shipping AI-coded apps where the icon and bundled assets are generated by a model and not reviewed by a human designer, scanning the compiled IPA or AAB against OWASP MASVS using a platform such as PTKD.com (https://ptkd.com) catches third-party asset issues, hardcoded brand resources, and adjacent IP defects before App Review does.
