I am not able to download the Xcode from new MacBook Air. Here is the configurations
MacOS High Sierra Version 10.13.4
Xcode version to download - 9.3
Yesterday, I also got the same error while installing Xcode on my MacBook Pro. I am on macOS High Sierra version 10.13.4. I tried various methods available on various forums and Apple's website but to no avail. I believe most of the proposed solutions are not for High Sierra. I also feared it might be due to some residual file or I messed up somehow since I have already installed/uninstalled Xcode several times.
However, today I got some update for High Sierra and after installing it, I tried installing Xcode again and bingo!! It installed successfully. :-)
There is an issue with app store. Maybe poor network condition too.
Try downloading it form this link here https://developer.apple.com/downloads/index.action
Related
I am developing an app for iOS and also using Mac Catalyst to run on my Mac. The app runs fine on my iPhone but always shows an error on Catalyst. The code used to run fine before updating to Big Sur Beta 6 from Beta 5. Here's a screenshot of the error: . Also the error in code blocks for anybody who wants to copy it.
The operation couldn’t be completed. (OSStatus error -10670.)
Domain: NSOSStatusErrorDomain
Code: -10670
User Info: {
"_LSFunction" = "_LSOpenStuffCallLocal";
"_LSLine" = 3664;
}
--
System Information
macOS Version 11.0 (Build 20A5364e)
Xcode 12.0 (17210.1)
https://github.com/MysteryCoder456/VegieMato/tree/backend is the GitHub Repo if anybody wants to reproduce this (i.
Faced same issue after upgrading to macOS 11 Beta 6. Reported bug to Apple but meanwhile found workaround - Select Product in Xcode, select 'Show in Finder'. Launch it from Finder. Additional step, hopefully Apple will look into it.
The problem is solved with new Mac OS 11.0 Beta (20A5374g).
If your catalyst app has multi-window support, you may still need to kill your existing app before launching the new one.
I also had the same problem. (I say had, I guess I still do, however I have a workaround) My App had been developed as iOS / iPadOS with Mac support. All has been working great throughout macOS 11 beta builds. Until today that is, when I, as you, updated to Beta 6. Upon attempting to run for macOS target I get the same error as you have posted.
After some googling I found https://www.virusbulletin.com/uploads/pdf/conference_slides/2015/Wardle-VB2015.pdf and had a go at simply opening the app directly from the build folder. Hey presto, it opened without any problems, I even cleaned out the build folder and built it again to make sure.
This would appear to be a problem that the next version of Xcode beta should fix. Until then, unless anybody can suggest a better fix, this will have to suffice for me at least :-(
Sam
-10670
I was having this same error code upon installing a Developer ID Distributed, Auto Signed version of a catalyst app on a test machine, non M1 Chip, Mac Mini(Late 2014) with MacOS Version 12.0 Beta installed.
The solution was to close the previously installed version of the app. Before opening the new version that I Airdrop over to the test Mac machine.
Why is Xcode 9.3 eating up all the CPU when running playgrounds. It seems like “diagnostics” and “homed” are the two processes that are causing the fault. Apple seems to be really sleeping over this. No solution on the Apple developer website.
Is anyone also facing the same issue
I updated the version of Xcode to 9.4 and this bugs was solved.
You can download xcode in this link:
Download & Install Xcode 10 version without Premium Developer Account
I've an iMac 14,2 Late 2013 (i7) with a nVidia GTX 970 third part GPU. All stuff works well until these days with the appearance of the issue described in title.
I've the same issue with the follow configuration:
Sierra 10.12.0 GM2 build 16A323
Nvidia Web Driver 367.15.10.05f01 for build 16A323
Xcode 8.0 GM 8A218a
Today I've installed the new Sierra update and Xcode GM version, but I've the same issue:
Sierra 10.12.1 update build 16B2555
Nvidia Web Driver 367.15.10.05f01 for build 16B2555
Xcode 8.1 GM 8T61a
I waited for the release of these new versions to see if the problem was solved but without success.
Another strange problem that seems related to the use of the third part GPU is the Xcode - Open Developer Tools - Instruments: everytime I try to launch an instrument I've a transparent empty window.
Any help or idea to solve this issue is appreciated.
P.S. This issue NOT happened when I use El Capitan v10.11.6, BUT with this OS version and XCode 8 happen another issue related to simulators. Look here for details..I wanted to destroy my iMac.
Update (Swift 4): with High Sierra 10.13.1 and Xcode 9.2(9c40b) finally this problem is totally solved.
Simple question, I want to know if anyone has had any weird or annoying problems with developing iphone apps in Xcode after upgrading to Lion. I remember having issues when Snow Leopard first launched. Are there any early adopter penalties here?
A big one for me: no more PowerPC emulation via Rosetta in 10.7 - important to think about if you need to do testing for legacy PowerPC code.
Fortunately you can still use Xcode 3.2.6 though if you don't want or need to use Xcode 4.1 - if Xcode 3.2.6 is installed prior to upgrading t Lion then it should still work, alternatively there are instructions available for installed Xcode 3.2.6 when Lion is already installed.
I just had the problem, that I had to upgrade to Xcode 4.1 because lower versions of Xcode don't work on Lion. ;-)
You have to download the latest Xcode 4.1 to do development on Lion. 4.0.x won't work.
You also have to learn how to scroll down pages like a flight simulator (you can turn it off). If you got used to the neat gestures in Snow Leopard, then get ready to completely start over again with new ones (no going back on Lion). Three finger web page navigation doesn't work, 4 finger application switching doesn't work, and a new "explosion" gesture is used for desktop and mission control.
The only thing i have noticed so far is that if you run Xcode in fullscreen mode, simulator can't be on same screen... And yes, you have to download new Xcode 4.1 from appstore... Everything else is pretty much amazing :-D
When you try to install Xcode 3.2.6 on Lion, Xcode toolset is greyed out and marked as skip. There is a simpler way to install it then those once described above. Here is the steps:
Mount the developer tools dmg
Open Terminal and run these two commands:
export COMMAND_LINE_INSTALL=1
open "/Volumes/Xcode and iOS SDK/Xcode and iOS SDK.mpkg"
Enjoy.
Be prepared for the new Xcode to remove the /Developer directory as a part of its cleanup process. This will wipe out QT in the process since it's installed there as well.
So if you want to keep QT intact you should skip Xcode's cleanup step or install a fresh QT afterwards.
I'm having a problem getting my MacBook set up to build iPhone apps in xCode. The iPhone Simulator locks up and shows the "spinning circle" busy icon.
I've tried everything I can think of, including
resetting the simulator
tried all of the different hardware options
tried the two debug build choices in xCode.
uninstalling the SDK and completely reinstalling
I downloaded the SDK today - "xcode_3.2.2_and_iphone_sdk_3.2_final"
I'm just upgraded from Leopard to Snow Leopard (10.6.3). I've run all the software updates. xCode version says 3.2.2 (1650)
If it matters, my MacBook is 3-4 years old, 13 inch, dual 2.16 ghz intel cores, 2 gig RAM. I've never had a single problem with it.
I would be so grateful if anyone can help me
thanks so much,
if you have access to the 4.0 one, then try that, if not, then I would install a previous sdk version in a different folder (or rename your current developer folder or delete it, then install the previous version under /Developer) and run that one instead
I just finished installing the 4.0 SDK. I made a new windows-based iPhone app (HelloWorld) and tried a build/run (Simulator-4.0 | Debug)
Same exact behavior... The simulator appears and the rainbow spinning progress wheel just keeps going and going
I took a sample from the process ("not responding...") but it's pretty big and I don't see any way to attach it to this question.
thanks again