Xcode 6 Installation got stuck - xcode
I'm having weird issues with Xcode. I am trying to install the new Xcode 6 from the Mac App Store, but it got stuck at "4 minutes remaining".
Earlier I had Xcode6 GM which was working perfectly fine. I thought of downloading the new version from the App Store so I deleted the GM.
Did anybody else have the same issue?
I had the same problem.
Forgive the cliche, but I had to "turn it off, then on again" (reboot the MacBook) and only then could I re-click on the "Install" button, and it'd start downloading XCode, from scratch.
Previously, using the App Store "Check for unfinished downloads" just told me that I didn't have any downloads pending, yet in the App Store app, it had XCode stuck in the "Installing" state.
Update
It's that time again. iOS 8.4 has been released, but you can only get XCode to connect to an iOS 8.4 device if you've upgraded to XCode 6.4... but you can only do that if you've upgraded OS X to the latest version. Thanks, Apple.
And as usual, download times are appalling, even if (like me), you've waited a few weeks until after the release, to avoid the rush.
And when you finally do get to click on the Update button in App Store to update XCode, it changes to "Installing" but actually, it's busy spending the next few hours downloading, rather than installing anything.
You have to keep an eye on the download bar, just below the Launchpad icon on the taskbar, to check how far the painfully-slow download has got...
I'm really not impressed.
I quit App Store, then searched for XCode in my Applications folder, clicked it, after a few seconds the download status vanished and I was able to click it again and open the app.
If it's any help, I was in Software Update this morning updating to Xcode 6.2. For several minutes, the installer was also stuck at the 4 minutes remaining mark, and then started changing the time remaining (swapping between longer and shorter intervals). From what it looks like, this is a UI issue (probably not estimating all the time it takes to install all components), more than anything else...
After clicking Install on Xcode in the App Store I got a busy-indicator in the App Store window for a few seconds and then nothing, it still just read "Install" after leaving it sit overnight.
However, I was able to download the latest version of Xcode as a .dmg file at https://developer.apple.com/downloads. The installation process was smooth from there.
In App Store, try "Store" menu -> "Check for unfinished downloads..."
I had a similar problem. Mine was stuck on "Paused". To fix it, I went to "Applications" (command-click the old version in dock -> gets you there faster) and moved to trash the Xcode app that was 337 kb in size. Then rebooted, went to the App Store and started the installation again. Turns out mine was "paused" on 2.27 gb (though I simply left my mac unattended, since the download was taking forever, and returned hours later).
Hope this helps someone, as I could not find an answer to this myself anywhere else.
I got the same problem. I updated to the last version of OSX, and then the update came automatically as a a result of that update.
I have stuck many times, this saved me. Now you try your luck on this
Apple should really consider having some more indication of install progress. Hard seeing any progress with the bar alone when installations exceed a certain amount of time. But then again I see apples security considerations indicating more detailed logging of the progress. I guess they oversee the few situations when updates are in the gigabyte range.
It may seem like a cancellation of the install , and going on for a second time, gives a faster install. But I would guess thats only because some of the install progress is cached.
My tip is; wait it out.
Related
Stuck at “Authenticating with the App Store...” when publishing my app [duplicate]
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
How long should Xcode 7 installation take
I am trying to install Xcode 7 for the fifth time. I always complete the download but the installation does complete. Currently, I've been waiting for over 3 hours for installation and it's still not done.
It's not the installation that is actually taking the most time, but verification of Xcode, once it's downloaded. Like yourself, I was wondering what was going on, but found it best to let it run its course. It would be better if there were some type of progress indicator during the process.
Seems to be a memory issue, for 4GB ram will take about 3 hours, and for 16GB ram will take about 30 minutes
I was fighting with the same issue for few days, and I found out that none of above answers is complete. Go to developer.apple.com Login Go to downloads (don't click on xcode yet) Go to see all downloads Now navigate to find your desired version of xcode Download .dmg file Unless you follow those steps you might end like me - being redirected over and over again to the appstore page (and download there was never ending)
xCode 6.1.1 slow and keeps freezing
I'm having some trouble working with xCode. It just keeps hanging and using 100% CPU right after a couple lines of code. I'm working on a new project and it barely has two files and it has become completely imposible to work with. I tried reinstalling xCode and starting my project from scratch but it won't work. I noticed three things that may help someone find out what it's going on. It's slow even when typing, the characters appear delayed on the screen. It keeps saying indexing on the task bar on top. If I clean the project it will disappear but come back whenever I start working again. It overheats as soon as I open xCode And here's some other facts that might help I'm running xCode 6.1.1 (build 6A2008a) My Mac is a mid 2012 MacBook pro 8GB Ram I did a fresh install of Yosemite a month after it was released, so it's pretty clean. I'm using the latest build of Xampp for my SQL server I'm using nodejs as a backend so I'm running an http with nodemon Hope any of you has a solution to this. Thanks and merry christmas to all of you. EDIT I found out that it will build just fine if I remove my conditional cast to NSInteger, NSString, Float, etc. I have like 8 of them one after the other, and just replacing as? for as did the trick. I'm curious as for why this is happening anyway though.
Similar problems on 6.1.1 (but also source kit crashes) were improved (but not completely resolved) for me by deleting derived data.
Hammer for Mac constantly rebuilding
When using Hammer for Mac (http://hammerformac.com, v1.6.12), after saving a file, the app will rebuild the entire project. However, it has started to rebuild constantly without stopping. It doesn't actually rebuild a project because it is cycling through its rebuild cycle over and over. Only if I manually click "Rebuild Now" does it stop the cycle and actually rebuild and stop. Anyone know why this might be?
The issue you have described all this time ago, is similar to an issue we're seeing now on the El Capitan pre-release. It's related to FSEvents and the way messages are sent about changes to the file system. It's something we've seen sporadically in the past, but we're working on a fix for the latest issue in preparation for El Capitan public release. Disclaimer: I'm the new owner and developer of Hammerformac Best Steve
Upgrade from Snow Leopard to Mountain Lion / Mavericks in non personal & large scaled development environment
My company is still running Snow Leopard and we're thinking about upgrading to Mountain Lion (Edit: Mavericks) soon. We are developing iOS and Mac OS X applications and have a small break between the old projects and the new projects. What this means is, that we can start over with the new applications on the new version. But what happens to the old versions? They don't have ARC, Storyboards etc... I know you can switch off ARC but we want to make sure that we will still be able to commit updates to our old projects and we can't afford to put lots of time and effort in the conversion process. I spent some time reading the user comments below the xCode update on the AppStore and read that the new Version deleted old projects. Of course we have a backup but this makes me uncertain if it's the right step. Does anybody have experience how this works in a non personal environment? At home I'm running Mountain Lion and xCode converted small projects by itself. I'm just not sure about large scale projects... Thanks for your time! Edit: I will upgrade one system tomorrow and then try to post the results and maybe some tipps, important steps and things to be aware of.
Tipps what to consider when doing an upgrade: Before you start Take your time for a good backup! - You can regard data which is only located on one harddrive as non existend. Start with one system first and try out everything before doing the major upgrade. Installation Consider it takes way more time than it does at home! The MountainLion Download took >5 hours because of a symmetrical internet connection. Installation time was ~1 hour (MacMini 2009 - 4Gigs Ram 1067). + xCode Downloadtime ~1hour Before you install the new xCode make sure all your projects and your old xCode Dev Folder are backupped. When the installation routine asks you to delete your old xCode do so (I didn't do it and now I have to manually assign each project to the new xCode. I've to delete the old version manually too and it's a bit more complicated if you have to do the research which files you are allowed to delete and which not) Then you have to download the different xCode libraries. There goes at least 1 additional hour. Time of the downloading- and installation process so far: ~8 hours. (Keep in mind we've a slow internet connection) Projects Copy your projects and don't run your conversion and tests on the original. When you open the project you'll probably receive lots of warnings. Don't Panic! When clicking on the "Validate Project Settings" warning xCode will suggest to convert your project for you. I've done this for 3 iOs applications (Build Target: 4.3) now and it worked every single time. Let it create a snapshot for you. Just in case. If your app has already been code signed you'll probably receive the "Target Integrity" warning. In every single case it worked for me to edit the path for the "entitlement.plist". (Just click the warning and edit the path at "Code Signing Entitlements") It may happen that you've to change the deployment-target. To do so go to the Project Navigator (cmd + 1), click on your project's name and then Summary. There you can edit your Deployment Target. If you get warnings on deprecated methods you should search stackoverflow.com for your particular case. If it has to do with NSURLConnection look here. To be continued...