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)
Related
I recently got a developer account from the company I work for.
When I log into Xcode with that account(or any other developer account) and open the company project xcode process keeps downloading data from developerservices2-rno.apple.com which I found out using wireshark.
as soon as I log out it stops downloading. and it doesn't happen when I open other projects.
this download averages about 1GB per hour and it doens't stop as long as I'm logged into xcode.
Anyone can help me find a solution to this issue?
tried with xcode 12.5 and 13 beta both are same.
I try to update my windows but I got this message:
I tried to reboot service but it didn't work.
Current version of my laptop: Version 1709 (OS Build 16299.192)
I am afraid this will be affected to future releases.
I recently had a similar problem on my PC and my laptop. My error code was as follows:
2018-08 Update for Windows 10 Version 1709 for x64-based Systems (KB4023057) - Error 0x80070643
After much kafuffle and reading quite a few articles and Microsoft waffle pages I decided to do it my own "straightforward" way. This is my story, if it helps you I am content. Summary:
Close/save all open applications;
Run Windows Update TroubleShooter;
Find the latest Cumulative Update;
Run the Cumulative Update;
Allow the computer to do the necessary restart processing.
The description below is what I did. It worked both times for me; firstly on my PC and secondly on my laptop. The difference with my laptop was that I didn't repeat the download of the Cumulative Update as I had already done this for the PC, I just ported the Update to the laptop via USB; everything else was the same.
On the laptop the whole process took about 40 minutes, start to finish. I didn't time it on my PC as I was doing things in slow stages. The download of the update is quite large (900Mb) so watch out for download charges if your ISP makes you pay for such things.
All descriptions/statements below apply solely to me. I am describing what I did and what I think. Like with Microsoft and others, any decision by you to follow any aspect of my description is entirely at your own risk. For any "lawyers" out there, any reference to "you" or implications that I am telling you what to do is just an unintended flaw in my poor English grammar.
Save and close all the applications that are being used:
The Cumulative Update will requires a restart of the computer so, for me, it was best to save any data now and close all the applications I had open in an orderly manner.
Find and run the Windows Update TroubleShooter:
Search the web for "Windows Update TroubleShooter". The page I ended up on was this:
https://support.microsoft.com/en-gb/help/4027322/windows-update-troubleshooter
Click the appropriate download link on this page. I am running Windows 10 (Version 1709; x64) so, for me it was: "Download Troubleshooter for Windows 10"; it was a small file, around 200Kb.
The download file was "wu170509.diagcab". I always "Save > Virus check > and then run".
Run the Troubleshooter (I double-clicked it);
On its first page, click "Advanced", then ensure "Apply repairs automatically" is checked, and finally click "Run as administrator". It reloads itself, click "Next" and let it run.
Whenever it found a problem I chose the "Apply this fix" option.
When it reports that it has completed, close the TroubleShooter.
This took me about 10 minutes to do (I am slow and I was also trying to make a cup of tea!).
Find the computer's details:
Load the Settings page; right-click the Windows "Start" icon -> Settings -> System -> About.
Note the following:
Under Device Specifications, note the System Type (mine is 64 bit "x64")
Under Windows Specifications, note the Edition, Version and OS Build details.
Find and run the Microsoft Update Catalogue:
Open a browser (mine is Internet Explorer) in Admin mode ("Run as Administrator" from its icon's Context Menu - I don't know why you have to do this but you get an error otherwise on IE);
Search the web for "Microsoft Update Catalogue"; the page I ended up on was this:
https://www.catalog.update.microsoft.com/home.aspx
Search for the latest Cumulative update for your version. I entered the following search terms that relate to my system in this year "2018 cumulative update windows 10 1709 x64";
Top of my returned list (the latest cumulative update) was:
2018-09 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4464217)
Note its KB number and click on its Title.
An "Update Details" window opens; click on the "More Information" link and a web page opens, mine was:
September 17, 2018—KB4464217 (OS Build 16299.666)
Verify the KB number with the Microsoft Catalog number just to make sure.
I only proceeded with this Update because its Build Number was greater than my current one (from section 3 above); for me, going backwards sounds like a route to a bigger mess.
Once I was content I was going forward I went back to the Microsoft Catalog (closing web pages and windows as necessary) and clicked the "Download" link for this Cumulative Update (KB4464217); a "Download" window appears. Click the link to download it (it says 863Mb). My download took 5 minutes via an Ethernet connection (no idea on timing regarding a WiFi download).
Run and check the Cumulative Update:
When the download had completed (and after virus checking it), I opened its folder and double-clicked the file therein and let it run. It took about 30 minutes to do its work. Once started it needed no help from me so I wandered off and did other work.
Once the Cumulative Update had completed I let it do its necessary restart. This is in fact a couple of restarts and took about another 10 minutes to complete.
Once these restarts had completed I loaded my system and did an immediate Windows Update. It returned with no errors and reported that my system was up to date - Yippee!
Notes:
A. There was one difference between updating my PC and laptop. On the PC my Desktop layout was undisturbed, on my laptop the Desktop layout was reset. I have no idea why the difference occurred.
B. In the middle of writing this, when I got to describing the Windows Update TroubleShooter, I decided to rerun the TroubleShooter on my PC. To my surprise it reported errors. I had done nothing of any significance since applying the Cumulative Update and checking it, just some simple Powershell stuff (Microsoft product) and a bit of internet browsing like news and football results (via Internet Explorer, another Microsoft product). It seems to me that Microsoft are screwing up their own Update System! What clever people they are - not.
Good Luck peoples - Pay It Forward.
The following Microsoft forum article suggests that it is a Windows Update glitch:
Update for Windows 10 Version 1709 for x64-based Systems (KB4041994) — error 0x80070643.
The article further suggests that the OP there has the later build of Windows, and that the problem may be suppressed by hiding the update (how-to provided in the linked article).
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.
After working for over 5 years with Netbeans I wanted to give a try with Phpstorm suggested by a friend.
I downloaded a fresh copy of Phpstorm and imported in the IDE a fresh project. The result is TERRIBLE!
Phpstorm is terribly slow during startup.
Doing an SVN commit take 5 minutes and keep CPU from 182.3% to 192%.
Editing a simple line of HTML like Hello World take 5 to 7 seconds just to type the first opening character "<".
Working in this situation is a disaster moreover if I'm working on a MacPro workstation with 8GB RAM with 2 Core Duo CPU.
I really don't understand what is causing the issue.
I attach a screenshot.
P.s.
Netbeans on the same workstation is flying!
Thanks in advance to all help and suggestion
I've been working on a large number of git branches recently, and a coworker advised me to invalidate my cache & restart PHPStorm. It seems to have worked, but be warned - you will lose your local history.
In any case, File -> Invalidate Caches / Restart solved my issue.
There is no quick easy answer here to fix your problem, because it can depend on many things, like OS version, JVM version, other software installed (you get my drift). If you open the IDE, and go to Help -> New Support Request, and open a ticket, one of our support engineers will be able to talk you through generating a summary of the system that will enable them to help you solve this problem.
I'm sorry I can't be more specifically helpful here, but usually in this case it's a JVM or OS problem that can be fixed quickly by the team once they get your system specs.
Gary
Go into your settings, and under IDE Settings, click on "Editor"
Go to the -Virtual Space- heading, and make sure "Use soft wraps in editor" is UNticked
In my case the problem was new plugins.
In setting disable newly install plugins.
From the official forum:
Current tasks are displayed in a View > Status Bar (a bar in a bottom of IDE). It might show "indexing ..." or "scanning files to index".
close it works for me.
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...