App icon missing or misconfigured before submission
An app has to ship an icon, and an icon is configured in three places that can each be wrong independently: an asset catalogue has to exist, the target has to name an icon set, and that icon set has to actually be in the catalogue.
Why it matters
The most common failure is a target pointing at an icon set name that no longer exists, usually after a catalogue was reorganised or an icon set renamed. Xcode does not treat that as an error you can see at a glance, and the build produces no icon.
The second is a project with no asset catalogue at all, which happens with projects generated outside Xcode or assembled by a template that never added one.
The third is a catalogue and icons present, but no primary icon set selected for the target, so nothing connects the two.
All three share a symptom, which is why they are worth separating: the build succeeds. Xcode does not refuse to compile an app whose icon it cannot find, so the first sign is usually a blank icon on a device, or an upload rejected for a missing icon asset long after you thought this was settled.
The icon also has to be complete for the platforms the app ships on. An icon set assembled for iPhone and then reused by a target that also builds for iPad or Mac can be missing sizes that only that platform asks for.
How to fix it
- Open the target’s Build Settings and find ASSETCATALOG_COMPILER_APPICON_NAME. That is the icon set name the build looks for.
- Confirm an .appiconset with exactly that name exists in an asset catalogue that is a member of the target.
- If the name is wrong, either rename the icon set to match or point the setting at the set that exists. Either works; what fails is the two disagreeing.
- Check the catalogue is a member of the app target rather than only sitting in the project, which is the case that looks correct in the navigator and builds without an icon.
- Archive and install on a device, and look at the Home Screen. It is the only check that distinguishes a configured icon from a configured icon that resolves.
The guidelines behind it
Read from Apple’s App Review Guidelines as last updated October 16, 2026.
Worth knowing
This is the one rule ReviewAhead does not run against an uploaded build. A build carries Assets.car, the compiled result, not the catalogue, so the check would report a missing icon for an app whose icon is right there. The report lists it as a limitation instead of guessing.
What ReviewAhead checks
App icon configuration. A submitted app must ship a configured app icon set.
- That an asset catalogue exists in the project at all.
- That the target selects a primary app icon set.
- That the named .appiconset is actually present in the catalogue.
- Reports the icon set name it found configured, so a mismatch names both halves rather than only saying something is wrong.
Apple’s own documentation for this requirement: developer.apple.com. Where this page and Apple disagree, Apple is right and this page is a bug.