'App store connect operation error asset validation failed

Hi I got this error while uploading archive with xCode.

enter image description here

Does anybody had this error before ? Thanks



Solution 1:[1]

I exported IPA from Organizer and used Transporter app which finally helped me to see the issues.

enter image description here

Solution 2:[2]

  1. Install the "Transporter" app from the MacOS app store.

  2. From Xcode's organizer, select your archive and press "Distribute App"

  3. Instead of "Upload", select "Export" and proceed as usual.

  4. Drop the exported .ipa into the transporter and press "Deliver".

Solution 3:[3]

I had the same problem. Even though validation continued to fail, I eventually just tried clicking on the "Distribute App" button in Organizer. That also failed, but gave me a much more helpful error message. Turned out that the issue had nothing to do with Assets. I added a redirect uri scheme that contained an invalid character. I fixed that, and the validation succeeded.

Solution 4:[4]

In my case, it was the version number. Once App is published on App Store, to push update use a higher version number e.g 1.0.1 (if in production we have App version 1.0.0).

Solution 5:[5]

I am also encountering this error with an Ionic project. Even though my build failed Xcode validation, I tried to distribute it to the App Store anyway, and received the following error, which provided more detail:

Missing Info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'xx.xxxxx.xxxxxxxx'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7. With error code STATE_ERROR.VALIDATION_ERROR.90713 for id 97fb5968-9248-4336-a622-e015181dd333

In Xcode I examined the app/app/assets and under AppIcon the 1024x1024px icon was missing. I added a file, generated a new build, and subsequently was able to Archive, validate and deploy.

Solution 6:[6]

I was getting the same error but when i tried to upload the app, it gives me the detailed info, i was using the same version for the latest build which apple doesn't accept. I just changed the version number for that build and able to upload the app successfully.

Solution 7:[7]

This error message occurs by different situactions, to address your problem you can distribute your app directly to get more detail error message.

I got same message because I overrite my ios folder with a older one, issue fixed by replacing a ios folder with a new one.( you can run "flutter create newProject" to get it)

Solution 8:[8]

  • Check if the new version is greater than the previous version.

  • In the issue navigator, you just need to apply the changes recommended by Xcode. Start clicking the issue to see the recommendations, it will prompt automatically.

  • Download Transporter, to see the details of the error.

    • You need to export appName.ipa from Xcode
    • Upload the appName.ipa in the Transporter

Solution 9:[9]

There is something wrong in your assets. Either the app icons are not correct/missing OR you need to check your images.

Solution 10:[10]

I just changed the iOS build version 3.6.3(92) to 3.6.4(92) from runner and it works fine. So, try changing your build version properly.

Solution 11:[11]

In my case two mistakes, I did

The first one is the store version and Xcode build  versions are not matching 
The second one is something wrong with our assets. (Either the app icons are not created/missing or other images)

Solution 12:[12]

I got the same error message when I tried to validate my app, so I tried to distribute the app and I got a full error message, in my case was:

Invalid Provisioning Profile Signature. The provisioning profile included in the bundle 'netoloboapps.com.mensagensProntas' (Payload/Runner.app) cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. (Expired profile signing certificate.) For more information, visit the iOS Developer Portal. With error code STATE_ERROR.VALIDATION_ERROR.90165 for id b493faef-bcf5-4732-995d-f7c6609a0354

My problem was a expired signing certificated. So here's the tip, check out the complete error message and see the source of the problem.

Solution 13:[13]

I got the same error too. I contacted Apple and received the following reply:

Thank you for contacting Apple Developer Program Support.

We are sorry to hear that an error message is displayed in Xcode and that you are unable to distribute the app.

We have checked our available resources and found that none of them correspond to the error you have inquired about.

We have identified a guide that may be related to the error you are experiencing and are sending it to you below.

Validate an archive of your app

If you need more information, please consider visiting the Apple Developer Forums, where you can discuss development issues with Apple engineers and other developers.

Developer Forums
https://developer.apple.com/forums/

For feedback on Xcode or to report a bug, please use the Feedback Assistant.

Developer Feedback Assistant
https://developer.apple.com/jp/bug-reporting/

We apologize for not being able to help you with your inquiry, but we hope the above resources will be of assistance.

Solution 14:[14]

I found same issue, but i dont see error reporting anywhere. I build my app with Flutter and i try edit version in pubsbec.yaml. and i edit too version app in xcode. then my app success validate and distribute

Solution 15:[15]

The XGA-sized icon for the App Store cannot have an Alpha channel (and only that one - all other assets are OK with Alpha channels... go figure). It's one of the many, many unnecessary quirks Xcode / AppStore Connect have that drive me nuts.

Solution 16:[16]

If you have already deployed (to the app store) the same version of the app you are attempting to validate for TestFlight, you will see this error message. The new TestFlight release must have a succeeding version number in comparison to the latest version of the app, if it is already on the app store.

Solution 17:[17]

In my case I was messing some AppIcon resolution images for iPad. Also I made sure that the version and the build are set correctly.