Related
Hi I got this error while uploading archive with xCode.
Does anybody had this error before ? Thanks
I exported IPA from Organizer and used Transporter app which finally helped me to see the issues.
Install the "Transporter" app from the MacOS app store.
From Xcode's organizer, select your archive and press "Distribute App"
Instead of "Upload", select "Export" and proceed as usual.
Drop the exported .ipa into the transporter and press "Deliver".
In case your current app version is already in approved but not released status, you cannot use the same version number. You must go higher version.
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).
Ways to fix this:
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
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.
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.
There is something wrong in your assets. Either the app icons are not correct/missing OR you need to check your images.
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.
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)
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.
In my case, the app was approved for release with the same version number. So I have to cancel the release to validate and distribute the app with the same build number. Or you can change the build number.
You can cancel the release in AppStore connect. It's a blue button on the top of the page.
Found that the problem was with the assets like it's said in the error. Don't know if it's a new requirement by apple or if it's an old one but you cannot have an alpha channel in your assets. So I just edited all my assets and deleted the alpha channels and then it worked ! Hope it help ;)
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.
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)
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.
Remove alpha channel only for the icon "App Store iOS 1024pt" (Assets.xcassets) and you will fix the issue "App Store Connect Operation Error - Asset validation failed"
In my case there were some errors with the icons in Runner/Assets.
I just deleted those images was shown in the image bellow and everything works fine.
If your app has "Approved" state, but it is not released yet - you can not use same version number.
You have two options:
increase version number (not just version code);
cancel release (nothing will be deleted, just your approval will be cancelled), validate and distribute app, submit for approval.
i have found a solution to this problem,
you need to double check that, you have check the iphone or Ipad checkbox on xcode , but you have to upload the Iphone icons or ipad icons, one of them is missing.
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.
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.
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
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.
1- Go to the icons folder
/myapp/ios/App/App/Assets.xcassets/
2- Open the photo
3- Click File, then choose Export
4- Deselect from Alpha and replace the image
This should be applied to all icons
I got the error when the WatchApp uses the healthkit api but not adds description into info.plist.
I use the Transporter App to upload, it shows the error summery.
For Flutter Developer, Change the version number. From Example in pub.yaml, 1.0.0+4 to 1.0.1+5.
If this is a new project and you are uploading to the App Store for the first time, you must have app icons set in the Assets folder.
This is why it could say "Asset validation failed".
The only one solution helps me is transfer app to other AppStore account.
Before uploading the app to the app store first we need to validate the app to check whether the app has any errors or not.
Another advantage of validating app is it’ll provide detailed error.
I found 3 scenarios on which this error will occur:
=> if we are not updating the version name
=> Alpha channel in all the images of Assets.xcassets/ should be removed (you can download alpha channel remover for that)
=> if we have selected Ipad in general settings Portrait, landscape right , landscape left should be enable if we have given just portrait mode we will face the same error.
Happy coding :)
Last week, with Xcode 7, I was able to upload without any issue. But today I am getting the message your app has changed to invalid binary.
I have seen that now with Xcode 8 a new icon 20x20 2x and 3x is added. I added one, but still getting the error.
Does anyone had similar problem?
Сheck your email!
In my case, I wasted a lot of time because I did not check my email. When you get such an error, Apple sends you an email with it's description.
For example, this is what Apple sent me:
"This app attempts to access privacy-sensitive data without a usage
description. The app's Info.plist must contain an
NSCameraUsageDescription key with a string value explaining to the
user how the app uses this data."
After days of wrestling with the same problem I finally got my app successfully submitted, but only after being on the phone with Apple Developer support.
A couple of things to keep in mind:
Make sure you set the Info.plist description keys for any entitlements. This is necessary for iOS apps. Mine was a macOS app, so this didn't apply.
Head over to iTunes Connect, and recreate all your provisioning profiles and code signing certificates if you're not 100% sure that they're valid. You can do it for both Developer and Distribution.
In Xcode, turn off automatic code signing for your app, and any build targets (you can try automatic code signing in Xcode after completing steps #2 and #4 but that wasn't what worked for me).
Go to Xcode preferences, and click your development team, and in the sheet that comes up, you should see some "Download" buttons beside the newly created (in iTunes Connect) code signing certificates and provisioning profiles. Click them all. And so you don't get confused in step #5, delete all the other stale provisioning profiles and code signing identities for this app.
In Build Settings for each of your targets, make sure that the Release build setting for code signing, and provision profile are set to the above newly created code signing certificate and provisioning profile.
Bump your build number.
Deep clean your project (Option-Shift-Command-K).
Archive build your app.
In the Organizer that opens up, select the newly archived app, and validate (it always validated, but I still would get Invalid Binary later).
Export the build and select the option "Save for Mac App Store Deployment" or similar.
When prompted, use the same Provisioning Profiles you used previously and save.
Open the .pkg in Application Loader which you can launch from Xcode > Open Developer Tool > Application Loader menu.
I was't getting any emails on the Invalid Binary issue. Instead, I was lucky enough to have set up my iPad with iTunes Connect, and so, like clock-work, I was getting notifications within a couple minutes of uploading the app: "Your app ... has changed to Invalid Binary."
If you don't get one of these Invalid Binary notifications, that's a good sign. Another 10-15 minutes later, I checked the iTunes Connect portal, and I could finally add the uploaded build and submit for review.
After a while of searching, as a last-ditch effort I added every possible 'NS...UsageDescription into each of my target's Info.plist and this seems to have worked. After process of elimination, I deduced that it was either the NSAppleMusicUsageDescription or the NSFaceIDUsageDescription key-string pair that was preventing the upload from being successful so I just added them even though I don't use either in my project. I have also read on some other threads that something with a new version of Xcode required them to have the NSAppleMusicUsageDescription even though they didn't use anything related to Apple Music.
Just updated to Xcode 7.1 and getting this error.
Was able to upload fine using 7.0.1
Hmmm, well a restart of Xcode, a fresh clean, build and archive seems to have fixed it.
If you encounter this error, you have two options:
Option A - Engage in an activity that takes a minute or two. Could be any of the activities described in the other answers, like re-install XCode, renew certificates, do a new build from scratch after clearing caches. Or simply go get a coffee.
or
Option B - Do nothing at all for a little while.
Then, try again. If it doesn't work, repeat.
Just updated to Xcode 7.1 and getting this error. Was able to upload
fine using 7.0.1
same here - restart, clean build, archive and upload was successful.
Same problem here. Grabbing a cup of ☕️ worked for me.
Exporting the app as an .ipa and uploading via Application Loader 3.0 worked for me. (Restarting xcode, cleaning, and re-archiving did not.)
I first tried to upload and got the "cannot verify client"-error.
Then i did a validate, which was successfull and then again a upload which also was successfull. No restart etc. needed.
Same problem here. Clean build and deleting project caches worked.
Had the same issue and tried everything including Application Loader but still would not load into iTunes Connect. I'm running XCode 7.1.1 and OS X El Capitan.
I also have Avira (free version) installed and once I disable it, everything went through. Hope this helps someone.
Stackoverflow has been my savior and goto source for Obj C and now Swift!!
I had this problem for all night. Got 🍵 ☕️🍺🍼 but didn't work.
Solved my problem only with:
Switching lan to wifi connection
Uploading App by Application Loader
Wasn't useful but i saw than in Xcode uploading start works as well after connection switching, so maybe was a connection my problem.
Clean project not work with me in XCode 7.2. But I solve the problem by export Archive and using Application Loader.
Step:
Archive you build.
In Organizer: Chose your archive.
Export "Save for iOS App Store Deployment".
Open Application Loader (Xcode -> Open Developer Tool -> Application Loader: Download it if you don't have).
Select "Deliver your App" -> Select your exported ipa.
Upload.
=> Done
I've been having this problem since Xcode 7.1 (for more than a month). I did everything I could trying to solve this: restart Xcode, clean project, clean build folder, build with a device connected, reinstall Xcode multiple times, even formatting the whole disk and starting from scratch. None of this worked.
During this time my colleague was always able to upload the very same builds to App Store without any problem.
Curiously, what solved this problem for me was disconnecting my non-Apple wireless mouse.
I found this out when I tried to submit an app from my home computer and got the same error. I disconnected the mouse dongle, tried again and it went through.
I've verified this three times both on my home (MacBook Pro 2013) and work computer (Mac Mini 2014).
This leads me to believe that during the app submission process Apple may check if your environment is purely made by Apple or not, and may block your submission based on that. This would explain the "Cannot verify client" message.
For what it's worth: I got this error when my startdisk was almost full (less than a few hundred MB left).
Cleaning up some space and re-submitting resolved this issue.
Experiencing the same problem. Tried a number of the suggestions above. Ended up using the Application Uploader instead.
Xcode > Open Developer Tools > Application Loader
From the rest of the answers it seems that a lot of different things "resolve" this issue. Here are the particulars of what solved it for me:
The iPad had to be plugged in.
The iPad had to be signed in (i.e. not locked).
After I satisfied those two conditions, it validates and uploads reliably. If either one isn't done, I am not able to validate or upload to iTunesConnect and I get the Cannot verify client (3000) error.
You can use Application Loader to upload your build and solve it!
Download Provisiononing Profiles of app on Apple Developer,
Quit and restart Xcode,
Run Provisiononing Profiles by Xcode,
Open app again,
In General -> get "fix" at Identity.
You can Archive and Upload to Apple Store
When it fails two times in a row, choosing "Validate" and after that "Upload to App Store" does the trick for me.
I tried most of the things here, but what finally did it for me was using the Application Loader instead of trying to upload my app from the Organizer.
Once I did it from the Application Loader I got an error message related to this: ITMS-90535 Unable to publish iOS app with latest Google Signin SDK, which was the real cause of the error.
I remade the app with "App Store" provisioning profile. Earlier it was "Ad-hoc" provisioning profile.
I submitted the app from "Application Loader" instead of traditional "Organizer".
Above two steps enabled me to submit the app to iTunes Connect for beta testing also.
There is always an element for surprise whenever apple releases an updated XCode.
After trying a few things, this is what worked for me:
Just before uploading your executable, validate it, you then have a modal where you get to pick your binary. On the right, there's the name of the provisioning profile used. There's an arrow next to it.
Click on the arrow which opens the finder to the location of the provisioning profile.
Delete this file.
Restart XCode
Clean
Rebuild/Archive
Upload
I just loaded Xcode 6 GM seed. Now I want to submit an update of my app.
Archiving works so far. But when I click "Submit", as soon as the upload loading bar appears Xcode crashes.
Do I need Yosemite?
I had to download the Application Loader from Apple because Xcode could not find it.
Do I need Yosemite?
No. Mine crashed the same way, so i uploaded my app using Xcode 5.1. It worked fine.
The Application Loader seems the only thing that works right now. Had the same problem, while uploading or even just validating.
Just export via Organizer and Upload via Application Loader helped.
I was faced same problem. Now it works fine.
Solution : Just accept new changed terms and condition from apple developer account and resubmit it.
Please Make sure you've accepted all of the new agreements & condition in the Member Center.
To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.
or just login to developer account and go to here https://developer.apple.com/membercenter/index.action
I was able to make Xcode work, but I had to go to iTunes connect and start the process there first by going "My Apps" and clicking on the plus sign. Fill in the info and hit save. Then try submitting with Xcode and it should work.
OK. Here's my $0.02.
1) Xcode 6GM crashes every single time for me. I am running 10.9.4. I have no idea how widespread the issue is, but it is 100% repeatable for me. I cannot use Xcode 6 to submit apps for review.
The crash happens during the upload. I have submitted a RADAR report and given crash logs.
2) I was able to submit using the App Loader. Here's how you do that:
2.1) In the Organizer, after you have done the Archive, select the latest archive for submit.
2.2) Instead of "Submit," select "Export."
2.3) Select the first choice (App Store).
2.4) Open the Application Loader.
2.5) Select "Choose."
2.6) Select the .ipa that you just saved in the export.
2.7) That will work. You may get a message teling you that the API file is too big for analysis. I got that for all 9 of the apps I just submitted. In my case, I ignored it.
I think they rewrote the whole application load from scratch, and that Xcode is still buggy as hell.
They had a deadline, and rushed it. It shows.
I expect both the server (Web) component and Xcode to apply patches soon.
In my case, I'm quite annoyed, as I had to rush out a fix for the arbitrary decision they made to change the way that the CLLocationManager works, which broke all my location lookups. The fix is simple, but there will be a period of time when I receive hate mail from the users that upgrade to iOS 8, and the app stops working.
Joy.
I just installed the official version from the App Store and now everything works fine.
I had the same problem. When XCode crashes during export or submit it means that you have non-valid certificate or provision profile in build settings.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
Double click new provision profiles you downloaded to install them, and then XCode will never crash.
The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)
After that, you can submit app and export Ad Hoc distribution for Testflight.
Been trying tonight to obtain a receipt for my app. However, I've been unsuccessful. Here's the steps I've done:
Code signed with developer cert
Made sure minimum version in the info.plist is 10.7
Checked for the presence of the receipt file and called exit(173) if not found
Built from XCode 4.2
Added a new version of the app and some in-app metadata in itunesconnect. The app status is now waiting for a new binary.
I've then done clean, build, right clicked on the app in XCode's project view and opened it in finder to launch it, hopefully failing validation and pulling a receipt back from the store.
However, this never seems to happen (don't get asked for any itunes login etc) and the app terminates immediately.
I've also gone through an entire build/archive/create installer type process as well but that didn't pop up the login either.
Am I missing something obvious?
Thanks!
I've finally got it working. In case anyone else has a similar problem, the real help for me was finding out about console.app. In running this I could see my app didn't appear to be signed.
I deleted all the certificates etc and re-installed new ones. Seems it HAS to be the Mac 3rd party developer. Nothing else seemed to work.