ITMS-90013: Corrupt Image File - The image file '' appears to be corrupt. about expo

[kadikraman]

Apple have confirmed it was an issue on their end and should be fixed now.

To fix this, rebuild your project with a new build number (unfortunate, but the build number was counted even though it errored) and resubmit.

[next6leo]

hi this happen to me as well using Managed build eas build local.

is working now when i resubmit guess is apple issues

[rodperottoni]

Started happening to my company's app this morning. Nothing at all changed since our last uploaded build yesterday - no icon updates, no package.json alterations, zero, nada. Currently unable to upload new app updates 😭

[Dung1128]

We've also just started having this error today. I'm trying a rebuild now, I can't upload it again since it says that the bundle version has already been used.

You need to upgrade the build version

[CacaoRick]

Now it can be uploaded normally, there may have been a problem on Apple's end just now (I didn't make any changes).

[Cryptodev9]

Yes, finally it works for me, I can sleep. I am using expo, the icon is in my app.json. it accepted my upload

[rodperottoni]

Comparing my last successful build with the ones I have now, I noticed the last successful ones had Expo CLI 6.3.10 included in the "Installed software". Wondering if this has anything to do with it ?

[rodperottoni]

A few comparisons between my last accepted build & the ones that are now failing:

• Seems like both files have the same checksum:

• File sizes are equal

• File permissions are the same: -rw-r--r--@

[Caspar-Fireant]

Can also confirm this just started happening randomly, no changes to any image files across the project.

[gmartpad]

Now it can be uploaded normally, there may have been a problem on Apple's end just now (I didn't make any changes).

Tested it right now. Yep, might have been a problem on Apple's end.

[aidankinzett]

We've also just started having this error today. I'm trying a rebuild now, I can't upload it again since it says that the bundle version has already been used.

[Dung1128]

I just encountered this error, now everything is back to normal even though I didn't modify anything

[Cryptodev9]

Still having the issue, Hello,

We noticed one or more issues with a recent delivery for the following app:

Nait
Version 1.0.4
Build 1
Please correct the following issues and upload a new binary to App Store Connect.

ITMS-90013: Corrupt Image File - The image file '[email protected]' appears to be corrupt.

Apple Developer Relations

[Cryptodev9]

I am just doing it on app.json, I have the icon here, the appstore image is not corrupted at all, it works on android why is there an issue with ios

[aidankinzett]

just confirming that the new build is still facing this issue too

[rodperottoni]

my builds are still failing - interesting that it started working again for some of you. 🤔

[Cryptodev9]

who said that its working

[CacaoRick]

I upload fail in 09:54 (UTC+8), receive email from Apple with same error.
But success in 11:18 with no code (and no icons) change.

This [email protected] is unnecessary because the current version can be set to use a Single Size icon for iOS app by providing only [email protected].
I see that the project prebuilt by Expo has set up [email protected] and Single Size settings, but Apple still rejects my upload (in 09:54 (UTC+8).

[willswinson]

Not React (native here) but found this thread as I was having the same issue across multiple apps. Seems to have resolved automatically for me, so Apple issue probably.

[sanghyeok-kim]

I had the same issue and failed to upload the Testflight,
Tried again an hour later with the same build without any changes and it worked.

Yes, It seems to be a random issue on Apple's end.

[next6leo]

Apple keep giving trouble to us developer.... [ITMS-91053: Missing API declaration - Privacy] is also one of it.

[deusdete]

I had the same problem 8 hours ago and tried again today, everything went well.

[shahbaz9118]

I faced the same problem 10 hours ago and tried again today without any changes except build number, everything went well and it deployed successfully.

[luckygogreen]

I encountered this issue last night. I haven't made any changes yet. I'll try resubmitting it and come back to share if it's successful.