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
Related
When I run tests on my project in XCode, it builds, and then says Testing... which never ends.
When I use the stop button, the process stops with this text in the console:
*** If you believe this error represents a bug, please attach the log file at /Users/MY.NAME/Library/Developer/Xcode/DerivedData/APPNAME-gcsubmsjksdbljcswbefkgugjray/Logs/Test/C53D8988-3564-4C2B-A535-075D26D1E4A7/Session-APPNAMETests-2016-07-13_140704-t3DFd5.log
However, I am unable to run the tests again, and have to relaunch xcode to run them.
Is this an issue on XCode that may be known to the Apple developers?
EDIT
So, I figured, the simulator is not launching in time, and that fails the xcode to run the tests. It might be an installation bug with the simulator.
As I anticipated in my edit to the question the first time, XCode installation did not install the simulator correctly.
I trashed the old installed version and reinstalled XCode. And now everything works fine.
Thanks for all the help.
I found that the tests never ran if I was running anything other than iOS10 on the simulator, so use iOS 10. I guess backwards compatibility doesn't really matter.
Im trying to get crash symbolication to work on Xcode 7. My app is already on the Mac App Store and I'm getting crash reports. The problem is that they are not symbolized. When uploading to itunesconnect I did check the option to upload the DSYM files.
If you notice on the screenshot below, the first 2 lines are indeed symbolized, but they belong to one of my frameworks not the main application. The main application is giving me a 0X10093d000 symbol repeatedly.
What could be the problem?
[Update: Still don't have all crashes symbolicated in 7.3, but for each crash condition, we can usually page to an individual crash report which is symbolicated]
Try XCode 7.3
For reasons unknown, we can only reliably symbolicate our latest production release with XCode 7.3, even though we didn't use it to create the release.
7.3 introduced some new errors and warnings, so if you do download it, I recommend you download it from Developer Center and install in a seperate directory which does not overwrite your current XCode 7.x install.
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.
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).
I am attempting to launch the iPhone simulator from Xcode, but I keep getting the following error:
Error from Debugger: Failed to launch simulator: Operation failed with underlying error: 4294967253.
I've found a number of posts where Xcode failed to launch the simulator, but none of them match the specific error code I'm receiving.
Glad you got things solved senfo. I've found that doing a full rebuild can work as well as checking your system console log for erroneous error message/warnings. Xcode unfortunately seems to be rather poor at conveying errors when deployments fail to the simulator.
Whenever I've had issues like this, Force Quitting the simulator from the dock (Alt-Right click), followed by Xcode seemed to do the trick. After doing that I could reload my project and it would run fine.
Failing that, I hear it might help to reboot your mac (though I've never needed to go that far).
I'm not sure why I didn't try this earlier, but installing the latest version of Xcode fixed the problem.