Since upgrading to Mountain Lion and XCode 4.4, I've been unable to step through code while debugging. 4.4.1 did not fix the problem. Sometimes it'll step 2 or 3 times, but trying one more step inevitably reveals the bug. Using breakpoints seems to work better, but still crashes on occasion. I've tried reinstalling. Crash log is here: http://pastebin.com/XmqJEVuH
Boss just told me to there's a Developer Preview of XCode 4.5. To my surprise, it actually works.
Related
I know similar questions have been asked many times.
My xcode projects ran fine on the simulator. Ive started a new project today and the first time I tried running it I get the black screen and 'unable to boot simulator error'.. and I have to force quit xcode. Now all my projects are getting the same error??? They were working fine before.. I have not updated anything either? Whats the problem?
Thank you
After many failed attempts at fixing the problem I ended up updating the OS from El Capitan to Sierra and I completely uninstalled Xcode and reinstalled a fresh version (from 7.3 to 8). The problem is now gone. I am assuming there was some kind corruption in Xcode as I cant figure how else this specific issue would occur.
Hi I just upgraded to Mountain Lion. I created an empty Single View Application and run it. The first time it runs fine but the next runs will give me the "There was an internal API error" pop-up warning TWICE. It's the same with my other projects. They run okay once but gets this error the next runs. There was no warning or any specific warning message of any kind.
Any idea how to solve this?
Would really appreciate your help.
I have it working on iOS6 Beta 4!! This is what I did but other variations may also work:-
Install XCode 4.5 Developer Preview 4
Delete your app from the device
Run your app from Dev Preview 4
Delete your app again (not sure if you have to do this)
Return to XCode 4.4.1
Run your app, stop running, run again!!!
Of course you could continue developing in 4.5, but I prefer to wait.
Installing 4.5 Beta 4 installs updated device support. Once this is done once (possibly on any device) it should work fine. If you use the same device on a different machine you will have to again run it once from 4.5 Beta 4 before using your preferred version of Xcode (You do not need to delete the app from your device this time).
Edit: I am pretty sure that if you make a change to your core data you will need to run from 4.5 for the first time also.
Don't know if this helps, but I've deleted all files in ${HOME}/Library/Developer/Xcode/iOS DeviceSupport and it worked as a charm (Xcode 4.4.1, OSX 10.7)
I had this problem when I upgraded my device to Preview4 but had my MBP still running Xcode Preview3. Updating to Xcode Preview4 made the problem go away for me, no restarts necessary.
Deleting the app manually from the device/simulator will allow you to build and run successfully. A long term solution is to not use a Beta Xcode :)
Sounds crazy but you can also not use the Beta version of XCode 4.
However, you must keep it in your left hand to authorize your iPhone to compile with the non Beta version (don't ask me why, it works).
If you run your app with XCode 4.5 preview & IOS6 Beta 4, the second time you run your app on the device, you'll get the internal API error.
In theory, you cannot use XCode 4.4 to compile on your iOS6 Beta 4 iPhone.
But...
It seems that, if you launch XCode 4.5 Preview, connect your iPhone (so it is recognized), run the application on it (even if you get the error), quit XCode 4.5, launch XCode 4.4 and .. tadaaaa... your iPhone is now recognized as an authorized device to compile on...
And of course, XCode 4.4 doesn't generate the api error...
I have Xcode 5.0.2 and iPhone with iOS 7.0.6.
Every time when I launched my project on iPhone, I saw "There was an internal API error". And it was launched on simulator without any problems.
I did all the stuff that usually helps (like remove an app, clean, restart Xcode, restart a mac, etc.).
This problem went away only after I restored the iPhone. Sad but true.
I don't know so far, why it appeared.
Sometimes when I try and build a project in Xcode, roughly 1 in 10 times, it crashes and quits. I then get an error box which says: "Xcode quit unexpectedly while using the libclang.dylib plug-in". Xcode will also sometimes crash randomly with no error report. I have never heard of libclang before, what should I do?
try installing latest Xcode 4.0.2 version
i'm developing iPhone apps. Yesterday i updated leopard to snow leopard. Alongside i made the jump from XCode 3.1.4 to 3.2.4
I was always quite happy with XCode - working most of the time under windows, I really appreciate how well the XCode toolchain works together.
however - i'm not happy with 3.2.4 at all. i experience a lot of flaws, mainly with debugging. When an error arises, the debugger often stops at another place than the actual error happened. Sometimes the debugger does not trap into breakpoints at all and i get after some time a Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack - whatever that means. And also I get invisible breakpoints which i can't remove anymore.
Does anyone experience similar things with XCode 3.2.4? if so, which is the newest release that works well?
Thanks!
Usually the problem is to do with level of debug symbols or some compiler optimization (which shouldn't be applied in debug builds). Maybe the information here will help.
Also try a complete clean (delete the build folder, remove the app from the device/simulator) & rebuild. Ensure you're working with the Debug configuration.
I've got 2 applications using Core Data with a sqlite persistent store. I've got a data loader routine that I run to populate the CoreData DB from csv files. During development, when my data changes I run the routine from the simulator to generate new databases and copy the new one into the project.
This has been working quite well for XCode 3.2.3 and iOS 4.0. It even works in the XCode 4 Preview 2 and 3. I just installed the final version of XCode 3.2.4 and iOS 4.1. Now my db loader fails. It gives me no message, no warning, no nothing. It just dumps out to the spring board and XCode gives me the "Debugging Terminated" message. It will fail at different times during the load so I'm pretty sure it's not a data issue. I'm not doing any threading. I assume the issue has to do with either Core Data or sqlite, since that's when the crash occurs, but with no info reported I can't tell for sure.
I uninstalled everything. Xcode 3.2.4, Xcode 4 preview (assuming it was an issue caused by XCode 4) and reinstalled XCode 3.2.3/iOS 4.0. Things returned to normal. After getting some work done I attempted to upgrade to 3.2.4/iOS 4.1 again. I uninstalled 3.2.3/iOS 4.0, rebooted. Installed 3.2.4/iOS 4.1, rebooted and tried again. No luck. Same hard crash. Same lack of messaging as to the cause.
I have determined that this only happens with the Simulator with XCode 3.2.4, the device is fine as is XCode 4 and 3.2.3. I've tried playing with the target OS selection (3.0,3.1,4.0,4.1). I've tired adjusting the Compiler from GCC 4.0, GCC 4.2,LLVM GCC 4.2, LLVM 1.5. I've tried setting the Base SDK to iOS Simulator 4.1. Interestingly enough it will work in the iPad simulator when using the 3.2 SDK. So I've at least go that as a work around.
I guess there is one of 3 issues:
An issue with my code that has been uncovered by 3.2.4.
Bug in 3.2.4.
A configuration issue that I've missed.
If anybody has any troubleshooting ideas or answers I'd love to hear them. I've been doing iOS full time since V 2.1 and I am seriously stumped.
Thanks in advance,
I figured out my issue. It looks like the CoreData/Sqlite connection was a total red herring. Following a tip I read on SO, I used OSX's Console application and got a critical message "Failed to launch in time" that was not being displayed in XCode's debugger console.
It looks like the process was being killed due to what is essentially a timeout error. The iPhone will kill an application that takes too long to complete "didFinishLaunching." That's where I was kicking the data load routine off from. The new version of XCode must have adjusted it's timeout values.
So my takeaway is give OSX's console a shot if XCode isn't telling you everything and watch out for those red herrings.
When I upgraded I ran into troubles in the simulator when saving the managedObjectContext. I finally deleted my sqlite CoreData store file and have not run into similar problems. Try deleting your data file (well save a copy of it before deleting to see what is different).