With a certain project in Xcode 9 beta 6 when I try to Upload to the App Store I get:
I am the "Admin" role for this account.
All contracts are up-to-date
I tried removing/re-adding my account from Xcode prefs several times
Submitting for the same project from Xcode 8 works (however I need to upload from Xcode 9 for this project because it links against iOS 11 beta)
Another developer on the team is seeing the same thing so this seems like it might be common. Anyone find a workaround?
I encountered the same issue with xCode 9 GM build and others reported it as well in xCode 10 and xCode 11. Deleting the derived data actually solved it for me. Hopefully it will help others as well.
Close xCode
rm -fr ~/Library/Developer/Xcode/DerivedData/
Reopen xCode and try to upload again
This seems to be issue with Xcode 9. Solution is to use Application Loader tool.
Step 1 : Create an IPA file
Clean your project from Product -> Clean (cmd + shift + k )
Select Product -> Archive
Once archive is successfully completed it will open in Organizer window
Press Export button present on right side
Now select the distribution method as per your need and click on Next button
This will show the App Store distribution options. Now click on Next button
Re-sign your project (preferred is Automatically manage signing) and click on Next button
There will be Review window containing IPA content details. Click on Export.
Now choose the location where folder is to be saved and Click on Export.
This will create an folder containing IPA, packaging.log, DistributionSummary.plist and ExportOptions.plist file
Step 2 : Upload IPA using Application Loader
Right click on Xcode tool present on Slide-bar. Goto Open Developer Tool -> Application Loader
This opens Application Loader. Press on Choose button and select IPA file.
This will analyse IPA file and will show IPA details. You can press on Activity button to see list of activity performed while uploading app. Click on Next.
This will create iTunes Connect API analysis file.
Once it is successfully uploaded it will show Success. Now click on Next.
You IPA file is submitted to AppStore successfully
The only solution I have found for now, is to generate IPA for AppStore and then upload it with Application Loader.
I just had this happen to me and this was my solution.
Full Quit out of xCode 9
Reopen xCode
Update to a new version number
Archive again
Result: It worked
It's a pretty basic fix, but hopefully it will for you too.
None of the mentioned answers helped me. Below I am mentioning what all I have tried to solve the issue but didn't work.
i) Check provisioning profile & Certificate combination.
ii) Clean
iii) Quit Xcode
iv) Delete derived data
v) Restart Xcode
What worked for me is
i) Open Xcode preferences
ii) Check iTunes account you are using. If it is already logged in, remove it.
iii) Login the iTunes account again
iv) Xcode will start process automatically once it gets access now.
v) Select the provisioning profile that you are using again while Xcode asks for it in the popup.
vi) Xcode will proceed upload process.
This worked for me. Hope it will save some of your's time as well.
I just had a call with Apple developer customer support. They said its a known issue and the team is actively working on it. But there is no timeline insight.
Following solution that worked for me.
Use Xcode 8 until Apple engineers fix this issue:
The solution may work even if you don't downgrade to Xcode 8
Steps for Downgrading form Xcode 9 to Xcode 8
1. Download Xcode 8 from:
https://developer.apple.com/download/more/
2. Install Xcode 8.
3. Create an ipa build
In Xcode go to
Menu -> Product -> Archive -> Export
4. Use the Application Loader to upload your ipa to iTunes connect
Application Loader can be found at:
In Xcode go to
Xcode -> Open Developer Tools -> Application Loader
Let me know if it helped
The same case happened to me.
Also when I tried to get crash reports, it shows that my session has expired.
I have just restarted my Xcode and it worked.
In My case none of the above solutions worked,
I have an access for both Developer account and iTunes Connect account, but I faced the same Issue.
The only option worked for me is updating my MAC OS before it was 10.13.4, after update to 10.13.6 the problem was resolved. Hope this will help to someone.
I've managed to get it working by creating a new user in iTunes Connect, with just the "Developer" role.
For me, that also required to creating a new Apple ID.
I then added that new user in Xcode:
Now it seems to work.
What works for me is to
remove the apple ID from the accounts known to XCode
to add the account again (do not import the account again)
See On Xcode 7 I keep receiving error "No accounts with iTunes connect access"
Edit: This worked for me in Xcode 9 GM. I don't know if it will be an issue in the final version
What worked for me is that I changed my regular AppleID email, with the equivalent #icloud.com alias.
For example, I didn't use myemail#gmail.com, I used myemail#icloud.com and it worked.
(Which I really don't prefer, I prefer using my personal email, but if it works, it works)
I could not use application loader because my password is not accepted. Even after changing my Apple ID password it was not accepted.
Restarting XCODE solved the upload problem this time. But it is a repetitive problem.
Apple is becoming a nightmare... XCode and iTunesConnect always have been...
I just removed and re-added my developer account for the Xcode 9. To remove account goto preferences -> select your account -> hit the minus icon(-). To add your account just click on the + icon next to it.
Restarting the laptop fixed this. Didn't try restarting XCode itself, just rebooted the whole laptop.
I also encountered with the same problem. But after I updated the Xcode to the current latest version of Xcode 9.2 solved my problem. I took the update on 2017-12-21.
For me remove derived data, clean project and try again working fine.
Please follow below steps:
Quit XCode
rm -fr ~/Library/Developer/Xcode/DerivedData/
Reopen XCode and try to upload again
Hope it will help!
Closed Xcode and reopened it. This worked for me. This was also the most popular answer on the apple forum. Do this first.
Your xCode must be open for longer time.
Quit the xCode and Reopen. It will work.
Got the same issue fixed with below steps.
Just do Quit XCode completely even dock too then wait for few seconds and Reopen the Xcode then proceed to Archive again freshly.
then believe problem solve :).
All the best.
Solution that worked for me in Xcode 9.1
Go to Preferences.
Go to Accounts tab.
Select the desired account.
If there is a login expired error displayed, login again.
Make sure the error has gone away.
Restart Xcode.
Try to upload the archive again.
Here's what worked for me (after trying many times of signing-out and signing-in):
Sign out your Apple ID (by going to Preferences with Cmd+,)
Sign in with your Apple ID, and make sure you sign in with ***#icloud.com
Somehow it all started working for me...
Posting it here in case it's helpful to anyone else. Have no clue how this solved the problem (and how the problem emerged in the first place).
Actually, it's apple server error. So, wait for some time and then upload. It'll work.
In my case this is the problem of firewall when I connected to other network it's working.
For me it helped to close Xcode and reopen it again, it was that simple ;)
Related
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
So basically Xcode 6.1 is crashing whenever it's trying to get team list. From the general tab in the main screen, when trying to submit the app to iTunes, trying to validate the app.. whenever it tries to get team list, it crashes. It is working fine an hour ago but when we added some team members in the iTunes account for internal testing, it started crashing.
Any ideas?
Same problem here, however it's possible to compile and generate a .ipa file by the command line interface:
xcodebuild archive -project $projectname.xcodeproj -scheme $schemename -archivePath projectname.xcarchive
xcodebuild -exportArchive -archivePath $projectname.xcarchive -exportPath $projectname -exportFormat ipa -exportProvisioningProfile “Provisioning Profile Name”
Hope this could help.
I was crashing too (while fetching teams) and I finally got it fixed...
Open Xcode -> Preferences -> Accounts
Check that each of the accounts is valid. I had two there that were expired/old developer accounts, no longer in use. I removed both of them and now the crash is gone for me.
Hope this works for you :O
We find a solution.
You could use Shenzhen. This is a command line util developed by Mattt Thompson.
Install:
$ gem install shenzhen
If you see permission errors, you can execute the command with sudo
After install, go to project folder and:
$ ipa build
Before, you need to configure your build settings on the XCode Project like usual.
More info and examples here: https://github.com/nomad/shenzhen
These save my day, I hope the same for you :)
Try uploading with Application Loader
Xcode -> Open Developer Tools -> Application Loader
Enter the iTunes Connect details.
TL;DR: If you think old accounts are to blame, try 'fixing' them by joining the Safari Developer Program (free).
Why I tried this:
I couldn't open the accounts tab or any dropdowns related to accounts. I had an old iOS Developer account, that had expired.
Ultimately I decided my old account was corrupt on Apple's side (somehow) and logged into their certificates page.
Not wanting to pay the $99 --to join the iOS program--, just to fix a crashing xcode I signed up for the free Safari Developer program.
Instantly my account in xcode stopped causing crashes.
Looks like Apple "fixed" the problem by Sunday (11/16). I was experiencing it too, and none of the suggestions worked for me. On Sunday it was magically working again.
I followed #cclogg's advice and saw that there was an expired account that was crashing. However, it wouldn't let me select the account without crashing XCode. I was only able to do this by selecting two accounts together and this prevented XCode from trying to fetch account information.
After that, I clicked on the minus button to delete both accounts. I figured it would be easier to re-add the second account. And now, the crashing problem is gone.
I'm having the worst time ever submitting an update to my Mac app. Everything was fine until I updated to Xcode 6. I'm in Mavericks, 10.9.4. I get the following error:
iTunes Store operation failed.
Unable to process application at this time due to the following error: iOS Apps must have a provisioning profile.
I have no idea why it says "iOS." Don't know if that's an Xcode bug or it thinks I'm making an iOS app. I used the same Xcode project file to submit the Mac app in the previous Xcode.
I have tried the following with no results:
• Revoked and deleted all certificates and provisioning profiles and started over.
• I created all certificates, provisioning profiles manually rather than Xcode managing them.
• Set the provisioning profile in "release" in the target and in a different occasion, in the project file.
• Gone into the project info and created a separate configuration.
The only "weird" thing I would say that I could be doing insanely obviously wrong is when I look at the options for code singing identity for release, it says "Mac Developer:yata" but there is no option for "Mac Distribution:(myname)" Should there be? I didn't need that in the past. Also, the only options that I can select are in a section called "identities in keychain." Should there be another section? "Identities in Xcode?"
Thank you for anyone that can help. I'll try pretty much anything at this point.
Solution for my case:
I got error in validation stage.
On organizer we see:
1) Go to Apple download page and download xCode 5.1.1
2) Double click on xcode_5.1.1.dmg
3) Copy xCode.app to Desktop
4) Rename xCode.app -> xCode511.app
5) Move xCode511.app -> Applications
6) Close xCode 6.1
7) Work with validation and upload in xCode511.app
UPDATED
8) Be careful ! ITC.apps.validation.prerelease_build_missing
I don't have Xcode right now, but here are the steps:
Delete your certificate and provisioning, both your mac and iTunes account
Regenerate the certificates and provisioning profile (distribution)
Download double click
Go to the account tab, then view account
All certificates and profiles will be listed refresh the stuff there
Clean and rebuild your app with the right provision and 3 party Mac developer
archive, validate and submit (select the right provison and match the app)
voila!
EDIT
Everything you will ever need to know :
https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/Introduction/Introduction.html
I was having the same problem... finally I click on Submit and it worked! It seems that the problem is on Validate only.
Okay so our problem was that our company name had an apostrophe in it ---- could have the same issue if you have quotes in your company name as well. I contacted Apple for them to change it and then uploading worked from Xcode 5.1.1.
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.
I have MAC OS 10.7.3. xcode 4.3.1 installed using different apple id as my macbook pro was used previously by my friend. Now when i try to upgrade Xcode to 4.3.2 it asking credentials for my friends account. Unfortunately App store clearly says you can upgrade an app using the account which was used to install the app.
How can i upgrade Xcode using my credentials?
Thanks in advance.
I am sure you would have solved this by now but just posting the solution here that worked for me..
Open Finder and navigate to Applications,
Ctrl+Click the application and choose "Show Package Contents" (Xcode in this case),
Expand the Contents directory and click the _MASReceipt directory to select it, Type Command+Delete to
delete the directory permanently---you will be prompted for your
credentials since this is a protected file.
Quit and restart
AppStore, then find the application. You can update with your new id now without deleting the old version of the app
Hope this helps someone coz it took me a while to figure out !!
Unfortunately had to answer my own question,
Simple Answer: NO, You cannot update xcode installed from another account.
Solution is to delete the existing installation and re-installing from new account.
To delete the existing installation, you need to delete it from Launch pad. You can do this by locating xcode icon in launch pad, long click on the icon till it starts dancing. Then delete it and wait for a while till the xcode.app is deleted from /Application. If you manually delete xcode.app from /Application, App store will continue to think its installed and will not allow you to reinstall in future.
Above solution is assuming you have installed xcode from the mac app store, usually versions later than 4.2. For earlier versions, just deleting /Application/xcode folder should work.
The solution is found:
I had this bug, it's related to Spotlight. The App Store used Spotlight in some way. My fix was to add the entire HD to the "Privacy" tab in the Spotlight System prefs pane, close the prefs and wait 30 seconds, re-open and remove your HD from the Privacy tab. Spolight begins reindexing. Re-opened the App Store and problem was fixed! Posting this here for others who might search later on. Also filed a bug report with Apple.
Source: https://discussions.apple.com/thread/2806858?start=0&tstart=0