Getting "Cannot verify client. (3000)" when trying to upload archive from Xcode to itunesConnect
XcodeApp Store-ConnectXcode Problem Overview
Just updated to Xcode 7.1 and getting this error. Was able to upload fine using 7.0.1
Xcode Solutions
Solution 1 - Xcode
Hmmm, well a restart of Xcode, a fresh clean, build and archive seems to have fixed it.
Solution 2 - Xcode
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.
Solution 3 - Xcode
> 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.
Solution 4 - Xcode
Same problem here. Grabbing a cup of ☕️ worked for me.
Solution 5 - Xcode
Exporting the app as an .ipa and uploading via Application Loader 3.0 worked for me. (Restarting xcode, cleaning, and re-archiving did not.)
Solution 6 - Xcode
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.
Solution 7 - Xcode
Same problem here. Clean build and deleting project caches worked.
Solution 8 - Xcode
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!!
Solution 9 - Xcode
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.
Solution 10 - Xcode
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
Solution 11 - Xcode
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.
Solution 12 - Xcode
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.
Solution 13 - Xcode
Experiencing the same problem. Tried a number of the suggestions above. Ended up using the Application Uploader instead.
Xcode > Open Developer Tools > Application Loader
Solution 14 - Xcode
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.
Solution 15 - Xcode
You can use Application Loader to upload your build and solve it!
Solution 16 - Xcode
- 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
Solution 17 - Xcode
When it fails two times in a row, choosing "Validate" and after that "Upload to App Store" does the trick for me.
Solution 18 - Xcode
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: https://stackoverflow.com/questions/32622899/itms-90535-unable-to-publish-ios-app-with-latest-google-signin-sdk, which was the real cause of the error.
Solution 19 - Xcode
- 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.
Solution 20 - 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