Trying to export an archive for Ad Hoc distribution but getting stuck with "fetching list of teams from developer portal" that times out in a minute or so and that is it.
Cannot export.
Anybody experienced that?
I've been experiencing this a lot with Xcode 6.4, and OS X Yosemite.
All other applications on my MacBook can happily use the WiFi, but this particular Xcode screen often hangs on the "Fetching list of teams" dialog, before timing out.
My solution: turn WiFi off on your MacBook, then turn it back on again.
Fetching list of teams issue
Suddenly, Xcode bursts into life again, and is able to get the list of teams.
(Sigh.)
Update
Btw, if this doesn't work, reboot your MacBook. That also fixes the problem.
I get this all the time, never saw it before and it started happening about a week ago and now it happens frequently. It looks like something on apple's server causing the problem. Attempts will go through eventually if you keep retrying. Some of the suggestions people are posting aren't actually fixing the issue, they are just doing something random and then retrying again later and it's just luck that it worked.
You can cancel the attempt quickly as when it works it will go through in a second or two, so you don't need to wait for the timeout to try again, just cancel it and retry.
Restarting wifi might help if you are having network problems and seems to fix the issue temporarily for some people.
Hope this helps and Apple fixes it soon.
I think iTunes Connect is having a few issues today. I've had numerous upload issues.
I know this might sound weird, but deleting and creating the archive worked for me. Hope it helps someone.
It was happening for me all the day. Not 100% sure why but I removed all of apple ids associated with apple developer portal in Xcode/Preference and added again only the one I need to use to upload the app. Solved the problem.
I believe some apple ids cause problems sometimes.
Hope it helps.
I ran into this issue today on Xcode 7.1. None of the above worked for me at all. Solved the problem by updating to Xcode 7.1.1.
I had this issue right after I added an account to my Xcode preferences, I don't know if there's a limit on how many one can have (I had eight at that point), but once I deleted the recently added account, it worked straight away.
I've had this issue before, and sometimes waiting or restarting xcode fixes it, but not always, in which case you can do everything from the command line.
First, create an xcarchive
xcodebuild archive -project PROJECTNAME.xcodeproj -scheme SCHEMENAME -archivePath PROJECTNAME.xcarchive
Then, export the xcarchive. You'll need to know the name of your provisioning profile (not the filename), which you can find in the Apple Development Portal.
xcodebuild -exportArchive -archivePath PROJECTNAME.xcarchive -exportPath PROJECTNAME -exportFormat ipa -exportProvisioningProfile “PROVISIONINGPROFILENAME”
If you need additional configuration for archiving, you can read the man page for xcodebuild
Answering my our question because I found solution that works for me (same as Accepted Answer by CodeSmith):
I am still getting this problem 50% of the times, but lately I found sort of a solution:
I noticed that when fetching stays longer than ~5 sec it never finds my profile and it always returns time out, so I just cancel it if it is longer than 5sec and start export over. Sometimes it takes 3-5 restarts, but eventually it goes through fetching very quickly ~1-2sec and shows my profile.
SO, DO NOT WAIT FOR IT! IT WILL TIME OUT, JUST START OVER.
No need to restart XCode or Mac, just cancel export and start it over.
Hope it helps somebody
Simply restarting Mac immediately helped me
Related
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.
I've had an iOS project in fairly stable condition up until Xcode 8's public release. After a bit of confusion with the Migrator, I finally convinced the compiler that I did not want to go Swift 3 yet, and that my code was indeed valid Swift 2.3. Not sure if this at all relates to what the Organizer does in validating my long-awaited archive with some long-overdue fixes for iOS 10, but we'll see...
Anyway, I got Xcode to archive my latest build (which runs fine on my iPhone 5s by the way). I tell Organizer to "Validate..." in preparation for an upload to iTunes Connect. After a good deal of doing its thing, it finally spits this at me:
Been at this for three days now. Application Loader gives me something similar, but not much more helpful:
Following the suggestions in this answer, I find that every single one of my compiled assets read as sRGB, not 16-bit, or P3. Aside: When does an API analysis file get "too large"? I mean, sure I use Apple's APIs a lot, but I can't be alone in that. That's what they're for, right?
I've tried (almost) everything I can think of. I've redone my code signing a dozen different ways, read and recombobulated the build settings wherever I thought could be relevant, and tried every combination of bitcode and symbol inclusion available to me. Just about everything I could come up with short of migrating to Swift 3! Could that really be my solution? It's a rather big jump, and with the time I have, I'd prefer to get this working build out to my users before I'm slammed too hard to shore up the updated codebase.
I can't seem to find anything on "ITunesSoftwareServiceAuthenticationErrorDomain", or this mysterious "error 434". The only reference I've found so far leads to a dead StackOverflow question. Really wish the author hadn't removed it... Wonder if he found his answer?
So my question is as follows: What am I doing wrong to get these errors, and how can I fix them? I'd rather not have to upload without symbols or bitcode, so if that's the workaround, I'd like to know why, so I'm not limiting myself for something dumb.
Cheers!
I had the same problem with Xcode 8.2 while submitting my application:
ITunesSoftwareServiceAuthenticationErrorDomain error 434.
Solution: I switched to different network and it worked for me.
Bump the build number and validate again.
Had the exact same problem. I tried upgrading to Sierra which seemed to update bits of Xcode etc. The new error message was formatted differently, so I could not see the "434"
(With 1 success in 15 attempts (I had to tweak a version number in a string in the app, so didn't choose to upload after that brief moment of joy), i just uploaded the archive anyway, and after 2 hours of processing, it was accepted. I will update when my new app version is live to verify this error can be safely ignored, at least in some cases (e.g. I checked all my graphics' color profiles, etc.).
Do the below steps :-
1. Analyze the project. (From Product Menu)
2. Click on Archive. (From Product Menu)
3. Select the development team for provisioning.
4. From summary window unselect "Include bitcode" and click on Validate button.
Now, It will working fine.
I solved it by uploading my app through Application Loader.
Archive app Export ipa iOS Deployment
Xcode-> open developer tool -> Application loader
I had the same problem while I was trying to submit the app to client's iTunesConnect account. I've signed in with new apple id, downloaded the certificates and provisionin profiles but still got this error:
(ITunesSoftwareServiceAuthenticationErrorDomain error 434.)
How to fix this error?
Try to remove Provisioning Profiles files at ~/Library/MobileDevice/Provisioning Profiles/
Make new Build and Archive the app. Xcode will create new Provisioning Profiles and submit the app to iTunesConnect.
Just to share this.
Quit xcode and re-login as suggested by members does not work for me. I solved it by using "Application Loader"
Steps: 1) change the version and build in your App 2) archive again for new file submission and export file to desktop 3) goto top menu: Open Developer Tool > Application Loader (if you don't have this , search, download and install this plug init) 4) upload the new version archived file. Done
You will find them in iTune Connect. From here process to My Apps > choose the rejected app > change the version and click on the new uploaded archive file, file will be processing..
5) time to resubmit :) cheers
Clicked Valid until it succeeded, 3rd time.
Since there seem to be many solutions to this problem, it may just be an issue not related to anything developers have control over and the "solutions" seem to be "solutions" because after some action was taken, it succeeded. The action I took was the non-action... and it was successful.
Hope this helps, as this is a stressful problem to have when you cannot upload your app and muddling around in Xcode to fix it you might break something else.
I fixed it by upload using Application Loader.
Besides, after upload the app i receive the warning about Privacy - Photo Library Usage Description and Privacy - Camera Usage Description, so that, please make sure you have them in your info
Hope it help!
I had the same problem. In my case it was caused by following. I had a lot of png-files in assets.xcassets and some of them had AdobeRGB Color profile. I changed the profiles to sRGB and xcode validated the archive with no error.
Frankly speaking, when I changed the profiles some other strange errors occured, but they dissapeared by themselves when I tried to re-validate the acrchive several hours later (I did nothing just waited).
If this occurred randomly, try to delete that archive and make sure you have "Generic iOS Device" selected as target when you run Product > Archive again. This solved it for me.
I Got the same issues when i try first time.Next time it Validated successfully. Please check network once before trying second time.
1.Cmd+Shift+K
2.Close Xcode
3.Open Xcode
4.Cmd+B
5.Product->Archive
Just Clear all file in Path ~/Library/MobileDevice/Provisioning Profiles
Go to Xcode Select Provisioning profile again and then it auto-generate again.
So It will be working fine.
In my case it was the following:
my account had been logged out and I had to enter the password again
Xcode v8.0 had to be updated to 9.x to be able to publish to the App Store (as of July 2018)
I fixed this problem by updating Xcode from 8.2 to 9.
Apparently there was a compatibility issue with an SDK used internally. Xcode was not helping with it's error message. I discovered it by using the Application Loader to upload the archive. Application Loader's error message made some sense.
Any ideas? It was working an hour ago, now everything is dead and the status page says all is good
try disconnecting any devices you have connected.
I just tried everything SO suggested, reboots, wifi restart, iphone hotspot, nothing helped, so I unplugged my device and suddenly xcode connected and teams were fetched.
Just to say, I've had this issue a few times in the past week.
I'm using Xcode 6.4 with OS X Yosemite (v10.10.2), and from time to time, it just hangs on the "Fetching list of teams" message.
Most of the time, it works fine, but then it'll start to time-out, or throw an error like this:
The solution: reboot my MacBook. It fixes the issue every time.
It's odd. All other applications can happily access the internet, but for just this one part of Xcode, it seems unable to fetch the data it needs, and only a reboot sorts it out. I didn't have this issue before.
And it's hard to identify if this is an issue with Xcode 6.4 or OS X Yosemite, and Xcode demanded that I upgrade to the latest OS before it'd let me update to 6.4 (so I could actually debug an issue with iOS 8.2) so both updates happened on the same 1-2 days.
Bug ? Bug ? Did I say "bug" ? Course not. It's an undocumented feature.
(Sigh.)
Five hours later
I've just had the same issue again...
However, this time, I turned off WiFi on my MacBook, then turned Wifi back on again.
And the problem went away.
It (almost instantly) managed to load the list of (two) teams that I belong to.
Hope this helps.
I know that is late for answer but maybe my solution could help others.
IT ALWAYS WORKS FOR ME:
Step 1:
Go to Xcode --> preferences --> accounts
Step 2:
Select your team name and click in view details
Step 3:
Click in
Final step:
Go to Window --> Organizer and try to upload again your app :D
i resolved this by deleting my accounts and setting them up again. none of the solutions above worked.
This worked for me by disconnecting from my WiFi then reconnecting.
Quit xcode and simulator. Open organizer and click on Upload again. This worked for me.
I tried adding the account again and also reconnected the wifi but it did not work for me but quitting xcode did.
Actually I think it is an issue at Apples server.
I just got through once 30 minutes ago but had set the wrong build version and now I get the same error again. I think we have to wait.
i had same issue when i had changed my account's password.
first time, i just authorized it through new passoword. (it's not working)
and then.
remove all appstore accounts on xcode
add same account with new password.
it work.
Just keep retrying, I suspect the issue is on apple's server side and retry attempts will eventually get through.
You should get the list back within a second or two, so you can cancel the attempt and retry quickly rather than wait for the timeout.
Restarting wifi seems to help some people but not others.
Check your internet connection.
Upgrade XCode, 7.2 fixed this for me.
I noticed that I had some connection problems.
The ethernet cable was not fully plugged in.
On wifi, make sure you have a good signal.
I had same issue, and I resolved it.
I got hint from #jab11
I have external storage for TimeMachine. Around a week ago TimeMachine start to fail backup my disk.
I plugged out external storage not properly When it happens.
So, try like below.
Plug in your external storage if you have one.
Check your partition's health. (In my case, I erased partition which is causing fail to backup)
open Xcode Organiser, then upload your binary.
I hope this help.
For me, I removed all accounts in XCode -> Preference -> Accounts and ADD account again, then it's working well.
I regenerate all of the certificates, update the version number of the application, but the problem persists.
Follow the below steps.
Go to My Apps Page.
Remove the Build. Then Save It.
Re Add your Build. then Save It.
Now try to Submit It must work.
I do not know what the reasons are, how to do?Thanks!
In Prerelease section the status of your build should not be "Processing". Just wait some time (10-20 min) after build upload, and it will be ready to use.
I got this problem in Chrome browser. Switching to Safari worked like a charm for me.
I had the same issue. To solve it, the unique thing I had to do was "Clear History and Website Data..." within Safari (version 8.0.3 in my case).
Please, keep in mind that I speak from my experience and that worked for me. I cannot guarantee this as a general rule to fix the problem. Nevertheless I can assure that I tried several alternatives explained here and the one I just described was the solution for me.
It seems to happen if you are too quick between the build finishing "processing" and it being attached to a version and the version being submitted. I just published two apps in quick succession and the second submission had this problem while the first was fine. The only difference - speed of clicking the submit button.
Logging out and back in made no difference - the "problem" is with the submission.
I removed the just uploaded build from the version and then re-attached it, proceeding as normal to submit the release to Apple with exactly the same build and submission artifacts as before, except this one "saved" and went into the review queue.
I got the strange but working solution.
I had tried submitting the app using Safari browser but it didn't work and showed same error. Submitting the App using Chrome worked for me in the first go...
I'm stuck on this too; and have had to work around several other iTunes Connect bugs just to get to this point. What were Apple thinking by releasing this iTunes Connect version? It's completely ridden with bugs!
Sorry, I've tried everything I can: Filing a support case with Apple appears to be the only 'solution' at this point.
Make sure the Version you have on iTunes Connect and the version you gave in the Info settings in xCode are exactly the same.
I had 1.0.0 in iTunes Connect and 1.0 in xCode and it kept giving me this error message. I changed it to 1.0.0 in xCode and it worked perfectly.
I had the same problem. just sign out and sign in again. it should work.
I had the following issue when submitting a build which was uploaded couple of days ago for test flight testing. Then figured out that the provisioning profile of the application has expired so I renewed the prov profile and downloaded and re-archived the application (by increasing only the build number ) and uploaded and submitted it. And it worked like a charm.
I guess apple need to be specific of these error scenarios
In my case we contacted apple and they said the issue is that it seems that we don’t have a correct certificate generated on developer.apple.com. We use Xcode automatic signing management. I refreshed correct profiles, rebuilt and I could submit successfully.
I had the same problem. Tried from different system and it got saved
I have several tester who have registered to testflight and connected their devices... they have different ios models... iOS 6 and above... but all of them share the same problem.
When they click the install button of an app from "safari" or the "testflight" app itself...
the app starts to download... reaches about 90% and an error message appears...."UNABLE TO DOWNLOAD APPLICATION. the "app" could not be installed at this time.
Now i have about 30 testers... 7 of them have the same issue... the others have succesfuly installed the app with no problem what so ever...
It seems completely random bug to me as there are no correlations between the phone models or ios versions... which are by the way all 6 and above....
So... what do i do. please help
there could be many reasons of it Below are some of those mentioned
You are using Developer profile instead of Adhoc Distribution profile
You are using app identifier that is different from the one that belongs to your profile
There could be issue with iCloud/Gamecenter enabled/disabled
In any case ask the testers to connect the device to PC/Mac open iPhone Configuration Utility and see the logs after you press install from the build in testflight.This will give them a deep insight of whats going wrong there.Hope this helps
For me Setting Build Active Architecture to NO... works and installed successfully
For my case, uninstalling/reinstalling the TestFlight app from testers' phones seemed to help, as though the installs had got into an irretreivably bad state.
For anyone else going through this, worth noting that iTunes Connect support couldn't help, and Apple Developer Support wouldn't help.
I just had the same problem, it seems testflight is down. It was not showing in the system status from the beginning but they updated it to reflect the period I experienced the problem.
I had around 70 testers, only one was able to download, that tester just kept on retrying.
It seems that the original problem was solved by using the proper provisioning profile.
But, for future googlers' record, I was getting the profile installation error (seen in the console log) 0xe800800b which seemed to be an uncommon error code as I couldn't find anything.
Finally, found something mentioning a "bad UDID" would cause a range of possible error codes and I had 19 old ones in mine (damn Select All).
Selecting only the few I really cared (and knew) solved the issue (never bothered to try to find which was the bad one).
i delete my adhoc provisioning profile after adhoc provisioning profile generated by xcode. it's working fine