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
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.
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
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 just updated to iPhone SDK 4 and am trying to debug on my device with 3.1.3 installed. Before the update, I compiled with Base and Active SDK set to 3.1.3 and all was well. After the update, I'm limited to SDKs 4.0 and 3.2--setting the base to 4.0 and iPhone OS Deployment Target to iPhone OS 3.1.3, I'm able to build and install on my 3.1.3 device, but receive the following error:
Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack
I'm not using anything specific to the newer SDK, as I haven't touched a bit of code, just updated the SDK/XCode. So what am I doing incorrectly? The application runs as expected on an iOS4-installed device. Are there changes to pre-existing API's that need to be weakly linked perhaps? Thanks for all help.
Have you tried removing the app completely from your dev device, doing a build -> clean all targets, and then build again to your device?
I found this answer on macforums. If it's correct, then you probably have a memory corruption problem in your app that is confusing the debugger. Perhaps over-releasing something somewhere.
This probably isn't related to the SDK you are compiling with. It's possible you had this problem in your app all along but it just didn't show up until things moved around with the new Xcode, SDK, etc.
EDIT - I just ran into this problem myself trying to update an older app of mine to 4.0. It would run fine in the simulator and would install and run on the device except it wouldn't run in the debugger on the device. Anyway, I finally decided it was the .xcodeproj file that was corrupt or bad in some way and created a new project, copied over my source files to the new project and now it all works again. It's a pain but it only took about 20 mins to duplicate all my settings and I spent a couple hours trying to get the debugger to work.
Myself (and probably many others) are concerned about "will I still be able to compile/install apps for v3.1.3 of the iPhone OS?"
And what version of xCode does it become IMPOSSIBLE to ever write v3.1.3 apps again?
(Without installing a second copy of an older version of xCode.)
I've read the mile-long document that Apple wrote on the subject... but it sure would be simpler to understand if they just LISTED the various versions of each... instead of writing long paragraphs.
If you have:
Mac OS version 10.x.x x
xCode version x.x.x
SDK version(s) x.x.x
you can produce apps for iPhone OS x.x.x through x.x.x?
Both my iPhone projects are sometimes giving a "build failed" error with no explanation of what the error is, and then a "clean failed" when I try to do a clean. I tty emptying the xcode cache but that doesn't seen to help. What normally clears it is re-starting my Mac. However, that has just failed to work.
Has anybody else experienced this? I'm using the latest version of the SDK on Snow leopard.
(My Mac has also completely frozen twice today to the extent that only turning it off at the mains seemed to revive it so not a good day).
Make sure you have enough disk space on your mac.
Then go and delete your build directory in the project. Close xcode, open it back up. Try to build.
Hope that works, its just a guess.
Your Mac froze? Twice? On the Same Day? Seems your Mac is in serious disorder, I would look for this first. Maybe the build problems are just another symptom of a bigger issue.
Also, apart from checking out Xcode's logs in Console.app and posting anything interesting, did you install Xcode 3.2 from the Snow Leopard DVD before installing the iPhone 3.1.2 SDK for Snow Leopard?
If you upgrade to Snow Leopard (w/ Xcode 3.1 installed), and then immediately install the latest iPhone SDK (before installing Xcode 3.2 from the Snow Leopard disc), you may experience grave problems like this one. I know I did.
It sounds like you have disk/file problems. Check the permissions on the files and directories in the projects build folder. If you've lost permission for one of the files, the clean will fail.