When trying to upload an App to iTunes connect in Xcode 8.3.3, I get the error:
iTunes Connect access for "Team-Name" is required. Add an account in the Accounts preference plane.
The account already exists and (in some cases) has been working without incident previously.
How do I get around this issue with Xcode so that I can upload my app to the AppStore?
Had the same problem,
First had to export the .ipa to disk using XCode and then upload to the AppStore with Application Loader tool.
It worked.
I suspect that Apple has broken something with the IOS 11, etc upgrades going on. It was all working fine over the last few months, including yesterday, and suddenly today its broken.
As a temporary solution, I had to use export to local disk (from Archive), then select: XCode/Open Developer Tool/Application Loader.
Had the same stupid problem.
Ultimately exported the .ipa to disk (via Xcode itself) and used altool command line tool to upload the ipa. It worked!!
altool --upload-app -f YourIpa.ipa -u <username>
Apple should really spend some $$$ on improving Xcode and the overall Developer experience. Its painful.
I again went back to Xcode to try and upload but met with the same error, so command line was indeed helpful.
A restart to Xcode did the job for me
I just spoke with an Apple rep, and he said I had to update to Xcode 9 GM and rebuild. After doing that, I was able to upload builds again.
On Xcode 9.3.3, a simple restart of Xcode fixed the issue for me.
This goes along with the other answers, eventually I had to export it and deliver the ipa with Application Loader.
However, Application Loader didn't initially work for me. I had to go into my apple id account (appleid.apple.com) and add an application specific password. Then I signed out of Application Loader and signed back in with the application specific password.
As far as I know, xCode doesn't let you sign in with an application specific password. My guess is that Apple broke authentication via regular passwords on their backend, but didn't break application specific ones.
It works for me to follow the steps:
Archive the app with Xcode 8.3.3.
Upload to iTunes Connect with Xcode 9 GM.
I started to panic this morning too, but then I remembered something like this happens every time a new iOS is released. Use Application Loader. Don't start changing certs/provisioning profiles. I'm sure Apple will fix soon. Plus Application Loader is super-easy to use. Good luck!
When nothing works. Just restart your computer and try again! Nonsense but works like magic.
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)
Same answer here: https://stackoverflow.com/a/46225187/4772647
I did as some of you suggested, I used the Export function in Archive/Organizer to export an .ipa, then go to the Xcode application, use the Show Contents, then nav to "Application" and "Application Loader" and uploaded my app using Loader and that all worked perfectly!
This happened to me when my app was rejected when uploading on AppStore (not sure if this could be connected).
I tried to remove and readd the Developer's account in XCode but that didn't help.
Then it started working after I replied to the Binary Rejected message on App Store Connect and restarted XCode.
Not sure if that could be connected but it started working again instantly after those steps.
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.
Related
The app is uploaded without errors, but when I press the install button I get this message:
I'm using macOS Sierra 10.12 and Xcode 8.
This has never happened to me in old versions of Xcode. What could be wrong?
TestFlight is currently unavailable, i can't either install from TestFlight or see any of my builds in Itunes Connect. Also my app was in processing for 4 hours, then this happened.
Please check here https://developer.apple.com/system-status/
or this screenshot
Update: Confirmed by Apple
I had the same issue. I never had an issue with setting or not setting the encryption flag. So I thought maybe they made a change today. So I added the key in and it still didn't work. I decided to remove the last build from testing then re-added it. That worked for me. I was immediately able to download and install the app. Hope that helps.
Build another version and upload to Itunes Connect.
Maybe your time uploading have some problem from Apple Server.
I have just checked.
Seems to be working for me this morning now. Incidentally Brad my app had GPUImage embedded in it so just for giggles I also added the "App Uses Non-Exempt Encryption." switch to the embedded GPUImage plist. Not sure if that was relevant.
2 days before I successfully uploaded the archive for my application and my application is on app store, but yesterday and today when I upload the archive I see "Uploading the archive" message (with subtitle "Sending api usage to itunes connect") at the beggining, but then I see "iTunes Store operation failed. This action couldn't be completed. Try again later" :
When I try to upload the archive for another application, everything is OK, it's very strange, because since 2 days ago I only changed the minimum age in the application from 17 to 18 (so I didn't change everything important in the application settings).
May be in happen because we use iAd network and apple notified that this network will be unavailable since July ?
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 7.2 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1
Try this
Xcode -> Open Developer Tool -> Application Loader -> Login with AppleID -> Choose your app IPA
may this help you
Another solution that might help is disabling bitcode when submitting the IPA through XCode. Not sure why but this worked for my colleague when he had the same issue. If you want to keep bitcode then Application Loader will work, as pradip kikani pointed out.
I saw this exact problem TWICE yesterday (14th April 2016) using Xcode 7.2.
I'd get either a
"This action couldn't be completed. Try again later"
or a
"This action couldn't be completed. Try again. (-22421)"
which one appeared to be random. I just kept trying and trying and eventually the upload succeeded in both cases. Apple are obviously being a bit ****.
Not the most technical useful answer but thought it worth mentioning.
I ran into the same issue today when I wanted to validate my app in Xcode 7.3.1. In my case, my provisiong profiles had all expired on May 01, 2016 as I found out in the Xcode "Preferences > Accounts > View Details". I clicked on "Download All" and got renewed profiles with an updated expiry date.
I tried restarting my mac and all that but nothing helped.
What actually worked for me :
Logged out from my developer account in Xcode preferences.
Turn off bitCode from build settings.
Changed the provisioning profile.
But im not sure which one of the methods worked cause i did them all at ones.
good luck.
Got Same issue today!! I found there is no "arm64" in my valid Architectures.instead there was one "arm6".
Updated Valid Architecture list resolved my problem.
While facing such issue you should take care of some points listed below:
Make sure you have added correct bundle ID & provisioning in to App
If it is correct than might be after updating it on developer account it was not updated on Xcode. So in that case go to Xcode > Preferences > remove Account & Add it again. Clean Xcode set provisioning in targets & Projects both
Once you done with above steps clean project & Prepare New Archive again & try to submit it
Important Notes:
Do not try to submit Build files from Beta Xcode versions
If you are using Application loader than make sure its version is greater than or equals to 3.0
Hope it will help you.
I solved a similar issue by changing the build number from 1.0 to 1.1.
I am using xcode 7.1 and trying to upload my app to the app store directly through xcode. While uploading I am getting a weird error:-
cannot verify client 3000
Note:- I recently made changes in the accounts (xcode preference section). Is this related to my error?
I also restart the xcode but issue still there?
I already checked this question on SO, but they say restart your xcode. But this does not solve my problem.
For my case,I got this error after selecting "Generic iOS Device" when archiving, however i plugged in my iPhone and selected it, then archived, I got no errors this time.(I also cleaned both Shift+cmd+k and Shift+alt+cmd+k before archiving)
I encountered the same issue the first time I tried to submit to app store with the target on my device.
What worked for me:
I retried a couple of minutes later without changing a thing and everything went smooth.
This is temporary apple server bug. Try it again OR Retry after some time it will fix the problem.
Thanks
There is no need to reinstall Xcode. Just wait a few minutes and try again and it will work.
I tried :
waiting days,
restarting,
deleting the developer account in
preferences,
submitting archives from a connected device,
submitting
archives from a iOS generic device.
Nothing worked.
I needed to:
create an archive (it was from a connected device),
in the organiser window select the export button (on the right hand side underneath the "Upload to App Store" button.
Select that the export is for app store distribution.
Wait.
Take a note of the location the .ipa file is saved to.
Go back to Xcode, then select the menu item Xcode > Open Developer Tool > Application Loader.
Select Deliver Your App, and select choose.
Navigate to your .ipa file noted above.
Select next, wait, next, check for any error message, send.
Hope this helps someone.
I got this error while uploading my distribution archive to App Store with selecting Distribution provisioning profile scheme -> Product -> Archive -> Upload to App Store. The error is based on I chose my real iphone device in Xcode by mistake. You need to choose "Generic iOS Device" and repeat same steps as I mentioned before.
You have to plug in your iPhone to your Mac and try to upload to AppStore again.
For some reason, validating the archive before uploading fixed the issue for me.
With Xcode 7.1, I could only make a successful build without bitcode. Try it out if everything else fails.
I resolved this by exporting ("export" in xcode archive organizer -> "to iOS App Store") and using the Application Loader instead of xcode to submit.
It is recurring. Seems to me like an internal error with apples identification service or so.
My definite solution:
Get yourself a cup of tea and try it again.
You can, of course, do some voodoo or change the target device or something, but re-trying after a while will do.
I have the same issue.
I did the below steps:
Step 1: Select Code Signing Identity for "Release"
Step 2 : Select Distribution profile
I tried to use Application Loader instead and it worked well. Maybe that helps
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.
This one worked for me:
Delete the Archive that failed during upload.
Clean the solution.
Rebuild the solution.
Archive the it.
Go to Xcode's Organizer, then Validate (this should be 'Successful').
Upload the build.
When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...
We have been trying to submit an app to the iTunes store using Application Loader for three days and keep getting stuck at the "Authenticating with the iTunes store" step.
We have read many forums (including stackoverflow) and tried what was suggested:
making a new provisioning profile
using different or multiple versions of Application Loader
changing proxy settings
rebooting the Mac
uploading at a different time of the day, etc.
We have even left it running overnight and have not had success with getting past this step. Unfortunately, no feedback is given about what the issue may be, and we have not gotten any error messages. We have submitted multiple apps without any difficulty in the past but are completely stuck this time!
How were you able to solve it?
This only started happening to me today (May 2017) and no answers in this thread solved my issue. The resolution for me was from here;
https://forums.developer.apple.com/thread/76803
Open Terminal. Change to home directory,
cd ~
Move the current transporter directory,
mv .itmstransporter/ .old_itmstransporter/
Invoke the following file to let Transporter update itself.
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
Wait till it updates, then open Xcode and attempt upload.
You have to agree to a new sign up in Application Loader. Select "Application Loader" under the "Xcode -> Open Developer Tool" menu (the first menu to the right of the Apple in the menu bar). Once you open Application Loader there will be a prompt to agree to new terms and then to login again into your iTunes account. After this any upload method will work.
Just wait. In a few minutes all will be ok.
Dec 10th 2019, Xcode Version 11.2.1, MacOS X 10.15.1
I was facing exactly same issue yesterday and I thought it might be network issues, at least it looks like so. But this morning I had tried couple different networks and several VPN connections, none of them is working!
The highest voted answer here asks me to reset a cache folder named .itmstransporter under my home dir, the run a program iTMSTransporter under a specific folder, but I can't find both of them.
But soon I figured that it is the cache folder for the people who uses the legacy uploader program: Application Loader, which is deprecated by Apple and can be no longer found in Xcode 11. Then I found that the latest Xcode has located iTMSTransporter here:
/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter
And its cache folder is here:
/Users/your_user_name/Library/Caches/com.apple.amp.itmstransporter/
I removed my existed cache folder, and run iTMSTransporter without any parameter, it soon started to output logs and download a bunch of files, and finished in 2 or 3 minutes. Then I tried again to upload my ipa file, it works!!!
CONCLUTION:
Either the old Application Loader, or the latest Xcode, uses a Java program iTMSTransporter to process the ipa file uploading.
To function correctly, iTMSTransporter requires a set of jar files downloaded from Internet and cached in your local folder.
If your cache is somehow broken, or doesn't exist at all, directly invoking iTMSTransporter with functional parameters such as --upload-app in our case, iTMSTransporter DOES NOT WARN YOU, NOR FIX CACHE BY ITSELF, it just gets stuck there, SAYS NOTHING AT ALL! (Whoever wrote this iTMSTransporter, you seriously need to improve your programming sense).
Invoking iTMSTransporter without any parameter fixes the cache.
A functional cache is about 65MB, at Dec 10th 2019 with Xcode Version 11.2.1 (11B500)
I was stuck at "Authenticating with the iTunes Store" today. I had used the same version and build number as a previous submission. After I updated the build number, the upload went fine. I don't know if it's related, or if it was a coincidence.
I had the same issue for months, I just removed hotspot shield and private tunnel applications from my computer and tried to upload my app and everything worked just fine. so I suggest if you have installed any VPN application on your computer, remove the application and then try uploading your app from either application loader or xcode's organizer.
Try answer mentioned in this Reference Link, it really worked for me and for others as well.
Mentioning answer here as well.
Open Terminal and run:
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
iTMSTransporter will then update itself, then you can try uploading in XCode again or via application loader.
There is no magic fix. Itunes is just working bad. Lately is having more and more issues and it takes more and more to update and send an ipa to the store.
I had this issue with AppLoader and Xcode organiser too and after trying multiple times it just went through.
Changing network connection helped.
Turned off wifi on my phone
Enabled 3G
Created HotSpot
Connected my mac to the hotspot and got through the authetication issue
In my case, I hadn't agreed to the newest Developer Agreement. Just run Application Loader once, click on [Accept] to agree, then quit the Application Loader and the Upload to App Store should work fine.
Following worked for me.
Open another instance of Application Loader.
( Select "Application Loader" under the "Xcode -> Open Developer Tool" menu)
"Agree" to the terms.
After completing Step 2. First instance of Application Loader proceeded to the next step and build got submitted.
I have also encounter the same issue. One possible solution is to go to Xcode -> Preferences -> Accounts and from the left menu select on App ID then click on the View Details and tap on the refresh button. while reloading you will get following error
The selected team's agent, 'ADMIN NAME' must agree to the latest
Program License Agreement.
If you will not get above error, Following solution will not work.
It means that you need to login into the developer account using Admin login and accept that latest agreement.
Then you will be able to upload binary on the app store.
The updated answer for Xcode 11.x.x and Transporter application, open terminal:
rm -rf ~/.itmstransporter/
"/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter"
Wait a while
Problem solved!
I'm running MacOS Mojave 10.14.6, Xcode 11.3.1 and Transporter 1.1.1, and always got stuck at the Authentication with App Store stage, no matter how long I wait, I tried uploading using Xcode, using xcrun altool, Transporter, nada.
Finally I got it working by exporting the ipa file to a new Macbook (10.15.3, Xcode 11.3.1, Transporter 1.1.1), and used the Transporter app to upload it there.
The key difference is the Transporter tool on my new Macbook asked for a 6-digit code as authentication while the old Macbook did not, I suspect the authentication token on my old device expired but the system didn't ask for a new one when trying to upload the app. I had 2-FA enabled.
So I think forcing a manual re-authentication when you upload the app is the answer, the only other difference is the MacOS version, but I didn't test if it'll make a difference.
I solved the problem by removing ~/Library/Caches/com.apple.amp.itmstransporter.
For safety, renaming will be better,
cd ~/Library/Caches
mv com.apple.amp.itmstransporter com.apple.amp.itmstransporter.old
Then, xcrun altool uploaded my ipa successfully.
By the way, I'm using Xcode 11.x & 12.2, macOS Catalina.
In 2020 Dec, the fix did finally worked for me was restarting my mac.
Today I ran into this issue, on Xcode 11.2.1 I solved it by going to Xcode -> Preferences -> Accounts -> Tapped on the '-' next to my Apple ID, then signed in again. This fixed it for me!
In April 21, 2021, I followed #DawnSong's answer, outlined in the image below but I also restarted my Mac and voila it worked.
Spec
Xcode 12.4
macOS Big Sur 11.2.3
You may try to relogin your ITC account via Application Loader.
Just try a different Internet connection. I tried all the solutions above but none worked. However, when I tried using my cellular connection (instead of my DSL connection that stands behind a firewall), it worked immediately.
It might be a network issue. If you are running inside a virtual machine (e.g. VMWare or VirtualBox), try setting the network adapter mode from the default NAT to Bridged.
All i did was duplicate my Application Loader.app in /Applications and
ran both Application loaders at the same time.
this solution is out there, it used to work for me, but today not even that! what I did and worked is that (2 instances) + uploading with XCode (organizer). Had to try a couple of times and it worked.
hope this helps someone, this bug has been there for quite a lot of time now() an apple doesn't seem to care too much
Another reason could be that you have changed the machine from which you're submitting the app. Or the user account on the machine. The new machine may lack the private key and/or certificate for the App Store. Although a certificate with the correct name is displayed in Xcode.
In this case, go to https://developer.apple.com -> certificates, use the plus sign (+) to add a new certificate (distribution), and follow the steps to request a certificate for the private key on your current machine. After installing the certificate, authentication may work.
For me I tried almost all the suggestions given above but the problem still reoccurred after the first success in uploading to App store. Until I found this website. In summary, do the following
Open terminal
Run this command:
rm -rf ~/.itmstransporter/
“/Applications/Xcode.app/Contents/Applications/Application
Loader.app/Contents/itms/bin/iTMSTransporter”
Note: this command(which is different from others above) will delete your ITMSTansporter folder and create a new one and ensure that xcode is quitted before running this command.
3. Start Xcode and all should be well.
Using Xcode 12.3 Distribute App and xcodebuild both got stuck today at this point.
I finally was able to solve this. Peeking around my system I found 3 versions of iTMSTransporter.
Printing the version of each using ./iTMSTransporter -version gives the following results:
/Applications/Transporter.app/Contents/itms/bin/ has version 2.0.0
/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/bin/ has version 2.1.0
/usr/local/itms/bin/ has version version 1.9.3
So it looks that old version in /usr/local/itms was used by Xcode. After deleting /usr/local/itms I was able to upload my binary within Xcode 12.2 and using the xcodebuild command line tool.
Check your firewall
Network settings - (Check with network admin, usually they have blocked apple services unknowingly)
Check your system data/time.
I had same sort of issue, I resolved it by getting direct access to internet.
Also check Application Loader logs to see at which point it gets stuck.
I think I followed all the approaches given, but none worked for me.
My own approach that seems to work for me is to go thru the initial steps to upload a binary, then, after selecting the binary, do NOT click Send; instead close the window, and in the new window that will appear, start anew: hopefully it will go thru.
Found the solution:
I was uploading the build, Every activity went well except “Authenticating with the iTunes store”.
I disconnected my LAN cable and Connected my MAC with my mobile hotspot. and authentication problem was solved. If you have a limited internet plan then as soon as you pass authentication stage, again connect your LAN so that it will upload the app from you LAN cable's internet connection.
my upload failed each time when I uncheck the "include bitcode" option when uploading. So I checked the "include bitcode" option and upload went well.
Check your Firewall, If it is "On" then just Off it, then try