ITMS-90032 sounds like your whole upload is broken, but the cause is almost always small and specific: your app icon. Either the icon is missing from the build, or it contains transparency that Apple does not allow. Neither is a deep problem, and both are quick to fix. Here is what the error means and how to clear it.
Short answer
ITMS-90032, shown as "The upload is invalid" or "Invalid image path", almost always means your app icon is missing from the build or contains an alpha channel. Apple requires the App Store icon to be a flat, opaque 1024 by 1024 PNG with no transparency and no rounded corners, because the system applies the mask itself, as described in Apple's Human Interface Guidelines. The fix is to remove the alpha channel, confirm the icon is included in the asset catalog at every required size, rebuild, and re-upload.
What you should know
- It is almost always the icon: ITMS-90032 points at a missing or invalid image, usually the app icon.
- Transparency is not allowed: the App Store icon must be fully opaque, with no alpha channel.
- The icon must be present: a build that does not actually include the icon triggers the same error.
- No rounded corners: ship a square icon; the system rounds it for you.
- The fix is a new build: the icon lives in the binary, so you rebuild and re-upload.
What does ITMS-90032 actually mean?
It means App Store validation looked for an image and either did not find a valid one or found one it cannot accept. The message often reads "Invalid image path, no image found at the path referenced under key" followed by an icon key, which is App Store Connect saying the icon it expected is missing or malformed. The check runs at upload, before any human review, so it blocks the build from even entering review. Because it is an asset-validation error rather than a code error, the cause is in your icon files or how they were bundled, not in your app's logic. That distinction is worth holding onto under pressure, because it means you do not need to touch your source code at all: the entire fix lives in your icon files and the way the build packages them.
Why does a transparent icon trigger it?
Because Apple requires the App Store icon to be opaque. App icons are displayed inside a shape the system controls, so Apple flattens and masks them, and an icon that carries an alpha channel or transparent pixels is rejected rather than composited. A common path to this is exporting the icon from a design tool that adds an alpha channel by default, or using a PNG with a transparent background. The table lists what the App Store icon must be.
| Requirement | App Store icon |
|---|---|
| Size | 1024 by 1024 pixels |
| Format | PNG |
| Alpha channel | None; fully opaque |
| Corners | Square, because the system rounds them |
| Color | RGB, flattened, no layers |
How do you fix it, step by step?
Confirm the icon exists, flatten it, and rebuild:
- Check the asset catalog: make sure the App Icon set contains the 1024 by 1024 image and every required size, and that the set is the one the target uses.
- Remove the alpha channel: re-export the icon as an opaque PNG, or flatten it onto a solid background. From the command line you can do this with ImageMagick:
magick AppIcon-1024.png -background white -alpha remove -alpha off AppIcon-1024-flat.png
- Replace the icon: put the flattened, opaque image back into the asset catalog at 1024 by 1024.
- Regenerate for hybrid frameworks: if you use Cordova, Capacitor, Expo, or Flutter, run the icon generation step so the icons are actually copied into the iOS project.
- Rebuild and re-upload: the icon is part of the binary, so archive a new build and upload it again.
Why does this hit hybrid and AI-built apps more?
Because the icon pipeline is a step that is easy to skip. In a native Xcode project you drop the icon into the asset catalog and it is included. In a hybrid or generated project, an icon generation tool is supposed to create the sizes and copy them into the iOS target, and when that step does not run, or copies a PNG that still has an alpha channel, you get ITMS-90032 even though the icon looks fine on your screen. Design tools also export transparency by default, so an icon that renders correctly in a browser can still carry the alpha channel Apple rejects. The fix is the same, but the cause is the build step, not your artwork. It is also why the same project can upload fine one week and fail the next: a dependency update or a clean checkout can reset the generated icons, so a build that worked before is not proof the current one includes a valid icon.
What to watch out for
The first trap is adding rounded corners yourself; ship a square icon and let the system mask it, because a pre-rounded icon leaves transparent corners that fail the opacity rule. The second is assuming the icon is bundled because it shows in the simulator, when the release build did not actually include it; validate the archive in Xcode's Organizer before uploading, since that surfaces a missing or invalid icon locally rather than after a slow round-trip through App Store Connect. This is an asset error rather than a security finding, so it is separate from what a security review checks, but the rebuild it forces is a natural moment to verify the binary: a pre-submission scan such as PTKD.com (https://ptkd.com) reads the compiled IPA against OWASP MASVS for issues like exposed keys, so the build you re-upload is clean on both fronts.
What to take away
- ITMS-90032 almost always means your app icon is missing from the build or contains an alpha channel.
- The App Store icon must be a flat, opaque 1024 by 1024 PNG with no transparency and no rounded corners.
- Remove the alpha channel, confirm the icon is in the asset catalog at every size, and rebuild, since the icon ships in the binary.
- Hybrid and AI-built projects hit this most because the icon generation step can be skipped or leave transparency, so verify it ran and re-upload a clean build.
