This post relates to a rapidly changing event.
I am getting an error while trying to upload a build to iTunes Connect. This is the first time that I have seen this error, and I can't resolve it. I have tried following advice from other posts, but that has not proved successful. I have tried removing and re-adding my account in Xcode, having the client change my role to Application Manager, manually managing signing, and attempting to use Application Loader, which returns the same error.
I have two teams associated with my account; my personal team and my client's team. I am trying to upload my client's application, which I have done many times without issue. However, I just started getting the following error today:
I don't understand why this error has started occurring today after successfully uploading builds within the past few weeks.
Did something change on Apple's end that is now causing me to receive this error after successful uploads over the recent weeks?
As #AmodGokhale pointed out, this is likely a glitch on Apple's side. I just tried to upload with the Application Loader and can confirm that it works.
If you are not familiar with the Application Loader, here is how you do it.
Archive your project
Export -> Save for iOS App Store Deployment (save it where you can easily find it).
Xcode -> Services -> Open developer tool -> Application Loader
Deliver your app
Same issue here - I had to use the application loader.
As said above you have to generate an application specific password.
This can be done here:
https://appleid.apple.com/account/manage
Look for "APP-SPECIFIC PASSWORDS" in the "Security" section, and click "Generate Password…" I typed "Loader" for the "Password Label" and then cut and paste the password generation into the login screen of the Application Loader.
All seemed to be straight forward from then on.
Hi there i do what apple recommend and i will be able to upload my app using Application Loader.
Apple respond:
Thank you for contacting App Store Developer Support. My name is Camai, and I'll be assisting you today with your upload error.
We are aware of this issue and are working to resolve it. It occurs intermittently and might be resolved by retrying your delivery from Xcode. As an alternative, you can export your IPA from Xcode and upload it using Application Loader or altool.
For more information on using Application Loader and altool, please see the Using Application Loader guide: https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf.
If you have any questions, please don't hesitate to reply to this email, or contact us by phone. We are happy to help.
Worldwide Telephone Support
https://developer.apple.com/contact/phone
I was able to overcome the issue by uploading with Application Loader.
But there is a catch here, the Application Loader v3.6 which came with XCode works and the 3.0 version which was suggested by iTunes Connect portal does not work.
Go to XCode menu XCode -> Open Developer Tool -> Application Loader
Related
App Store Connect wont let me upload my app. Seemingly no matter what I do, I get this error when uploading via Xcode directly to App Store Connect:
"No suitable application records were found. Verify your bundle identifier ‘org.cocoapods.BigNumber’ is correct."
I know that this is a well known error, but still, others solutions didn't help me. The bundle ID (com.xxx.xxx) is exactly the same as in Xcode and I've updated all the pods with terminal. Currently I am filling out all the information about the App on App Store Connect, some said that would help. If so, I will let you know. If anybody has other ideas, please let me know, thanks!
You need to log into https://itunesconnect.apple.com/ and create a new app before you can upload your binaries via xcode.
-> Copied from a github forum, but yes that's what I had to to in order to make it work :)
For all those wondering: I did the thing where I had to set the product type/code or so (sorry, no access to Xcode right now) to 'APPL' (without the ''). All the time, I had it at 'AAPL' and was wondering why it didn't work. That's it :)
Rephrasing the steps, you have signed/built the app and are stuck on the last step to upload to App Store connect, just make sure you have:
Registered a Bundle Id/Provisioning Profile on Apple Developer.
Then go on and build your app.
Create an App on iTunes Connect(AppStore Connect) (Internally iTunes Connect redirects to AppStore Connect).
Then come back to XCODE, archive the app from Top Menu > Product > Archive and follow the rest of the steps as the same.
Refer to this medium article for the exact steps. This contains the latest steps with screenshots. These are the steps for uploading a flutter app to testflight but the idea is the same.
In my case rebooting my system did the trick.
This post relates to a rapidly changing event.
I am getting an error while trying to upload a build to iTunes Connect. This is the first time that I have seen this error, and I can't resolve it. I have tried following advice from other posts, but that has not proved successful. I have tried removing and re-adding my account in Xcode, having the client change my role to Application Manager, manually managing signing, and attempting to use Application Loader, which returns the same error.
I have two teams associated with my account; my personal team and my client's team. I am trying to upload my client's application, which I have done many times without issue. However, I just started getting the following error today:
I don't understand why this error has started occurring today after successfully uploading builds within the past few weeks.
Did something change on Apple's end that is now causing me to receive this error after successful uploads over the recent weeks?
As #AmodGokhale pointed out, this is likely a glitch on Apple's side. I just tried to upload with the Application Loader and can confirm that it works.
If you are not familiar with the Application Loader, here is how you do it.
Archive your project
Export -> Save for iOS App Store Deployment (save it where you can easily find it).
Xcode -> Services -> Open developer tool -> Application Loader
Deliver your app
Same issue here - I had to use the application loader.
As said above you have to generate an application specific password.
This can be done here:
https://appleid.apple.com/account/manage
Look for "APP-SPECIFIC PASSWORDS" in the "Security" section, and click "Generate Password…" I typed "Loader" for the "Password Label" and then cut and paste the password generation into the login screen of the Application Loader.
All seemed to be straight forward from then on.
Hi there i do what apple recommend and i will be able to upload my app using Application Loader.
Apple respond:
Thank you for contacting App Store Developer Support. My name is Camai, and I'll be assisting you today with your upload error.
We are aware of this issue and are working to resolve it. It occurs intermittently and might be resolved by retrying your delivery from Xcode. As an alternative, you can export your IPA from Xcode and upload it using Application Loader or altool.
For more information on using Application Loader and altool, please see the Using Application Loader guide: https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf.
If you have any questions, please don't hesitate to reply to this email, or contact us by phone. We are happy to help.
Worldwide Telephone Support
https://developer.apple.com/contact/phone
I was able to overcome the issue by uploading with Application Loader.
But there is a catch here, the Application Loader v3.6 which came with XCode works and the 3.0 version which was suggested by iTunes Connect portal does not work.
Go to XCode menu XCode -> Open Developer Tool -> Application Loader
I have built my application with deployment target 9.3 using Xcode 8.2.
Once I uploaded it to iTunes store it shows that "Uploaded Successfully" but the build disappears from iTunes after processing.
Can someone help me on this?
I got this issue many times.
Just check your email id which is attached with iTunes connect.
Your build has some issue and for that apple's developer team send email to you.
Fix that and upload new build.
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.