I've been using XCode 6.0.1 for a while now on a large-ish Swift project for iOS, and was wondering whether anyone else is experiencing these symptoms:
Sometimes it gets to the point that the spinner comes up on EVERY keystroke, and I have to wait 10 second before the next character appears in the editor.
Auto-complete takes up to a minute to auto-complete.
"Jump to Definition" takes up to 30 seconds to complete. Sometimes I've forgotten I asked for it, searched by text to find what I wanted, gone back to where I started from and then "Jump to Definition" kicks in.
I'm part of a development group of 3, and all three of us are experiencing the same behavior.
Yeah, I had this problem - this is a duplicate of this:
XCode 6 GM: Constantly freezing / locking while editing Swift code
I filed bug #18316444 and their response was:
Engineering has provided the following information:
We believe this issue has been addressed in the latest Xcode 6.1 beta.
This pre-release version of the Xcode 6.1 developer tools is required
when developing for OS X Yosemite, and includes the Swift programming
language. Xcode 6.1 beta runs on OS X Mavericks and OS X Yosemite
Developer Preview.
Please test with this release, and update your bug report with the
results.
Xcode 6.1 beta - Build 6A1042b
https://developer.apple.com/xcode/downloads/
Please let us know if that resolves the issue for you by updating your
bug report.
I don't know if this will help or frustrate you, but the problem eventually went away for me. What I did end up doing though was having an open terminal ready will killall primed for SourceKit. I wish I knew what changed, it just did. One thing to check though, on early versions of XCode 6, I kept running out of pty terminals - it would leak, run out, and then SourceKit would "jam up". I had to up it to 512, I think (whatever the default was, I ended up doubling twice). I can't remember if that also worked around this issue, or if it was unaffected.
If you remain afflicted, you might consider editing with 6.1 and doing final builds on 6.0.x.
Related
So, I'm currently working on pretty large project, which also consists of iOS application. Problem is, that few days ago, Xcode debugger stopped displaying variable values. I've tried to reset build settings, checked code optimization, enabled/disabled bitcode, tried older git commits, sadly with no luck. Also I've reinstalled Xcode, tried it on different systems, also installed El Capitan, to make sure, it's not some compatibility issue regarding Xcode 7 and Yosemite.
As you can see on the screen, when i try to print variable description, it displays error "Unable to determine byte size."
Could this be a bug? Application so far targets only iOS 9, so I wasn't able to test it on any non beta software.
Well, I've came up with at least semi functional solution, it is now working only on physical device, on simulator I'm still not able to debug.
What I did is, that I've set optimization level both on release and debug to "Fastest/smallest [-Os]" which doesn't make any sense, but it is working, so it's fine with me.
I'm experiencing a similar issue as was posted previously in:
WatchKit Simulator Won't Load App
My WatchApp seems to be loading okay (I'm watching step by step w/ NSLog), but the spinner (sometimes) never stops and the Watch interface (sometimes) never appears in the Simulator, i.e.:
I've tried some of the workarounds posted at the above URL (and I apologize for not being able to directly add my comments there) and they seem to work some of the time.
But I'm looking for confirmation that this is a bug in the XCode 6.4 Simulator code or perhaps an incompatibility with my older hardware? (I'm running latest version Yosemite & XCode but on an older mid 2009 Macbook Pro).
It just seems un-Apple like for a development environment to be this buggy. I keep thinking it's gotta be my code and not Apple's XCode Simulator?
Anyone else still encountering these kind of "spinner and not displaying Watch screen" in the Simulator?
Thank you for any input, the previously suggested workarounds seem to help some of the time but having to go thru that many steps with each compile & run cycle is making rapid iterative Watch development in the Simulator extremely frustrating.
I've been running Xcode with no issues, and all of a sudden playground sticks on Running Second, as seen in the image. Occasionally Xcode "stops" responding upon the launch of the project.
This takes forever and it's very hard to get a project going due to the time it takes to get start. Any ideas? I've spent hours trying to figure things out. I'm running Xcode 7 with Swift 2.0
It's a beta version of Xcode. The syntax checker crashed a lot on both Yosemite and El Capitan, for both beta 1 and 2. Compiler sometimes works, sometimes don't, and code works in Xcode 6 might not work correctly in Xcode 7 beta.
In the past, when Swift 1.0 beta just out, there were lots of issues like this, and some of them didn't get fixed till 1.2.
If this happens everytime, consider file a bug report to Apple so they could look into it. (I do!) Or you can provide some code you were testing so we can all have a look.
I had Xcode v6.0 - v6.1 . I'm not sure which one. What I can remember is, it does not support iOS 8.2
The problem is that my team and I release a game app for beta testing ( test flight pre-release , on iTunes connect ) . Every user that got iOS 8.2 crashes at the very beginning when they open up this game app.
After, I upgrade my Xcode to v6.2 which support iOS 8.2. It solve the problem. But still my team and I are not 100% sure if this will solve the problem long term.
My game app framework:
- Cocos2d-x v2.2.6
My question is that:
1.) Is Xcode version the reason it crashes at the first place?
2.) If so, do I need to update my app and my Xcode every time Apple releases new version of iOS?
Thankyou. :)
You need to investigate exactly what is happening, for example by connecting a device running 8.2 to a development machine and debugging. It is most likely that you have some bug in your code that can strike at any time due to random differences of the environment; for example uninitialised memory will have random values that can be different depending on the OS and will sometimes crash and sometimes not. It is quite possible to have a bug that has nothing to do with OS or Xcode version at all that behaves like this. And that bug can reappear at any time.
Correctly written code will work on all future OS versions without problems. With emphasis on "correctly written".
I have a apple watch app (in simulator) which used to swipe without problems between pages, but I noticed that in Xcode 6.3 beta this is unreliable (I raised a bug 19781821). Did anyone else have this problem or a workaround?
Since posting my original question, the bug has been (silently) fixed in Xcode 6.3 beta 3 (it was not mentioned in release notes). Using later versions including the Gold Master also work correctly.
This question is left now mainly to serve to document this past problem.