LLDB crash

How broken is syntax highlighting? If all the text is black, then SourceKit has crashed. If the keywords are colored, but nothing user-defined is colored, then the file isn't being indexed.Xcode 7 still seems to fail to display some errors (either live in the editing pane, or in the errors navigator, or both). Try building your project and see if that produces errors you haven't seen yet. Fixing the errors (and rebuiliding again afterwards) should allow you to get back on track.

I'm having the same issue: can't make calls, persistent freezes and crashes when attempting the most basic functions on Watch OS2 Beta. I also completely reset the watch and tried unpairing to no avail.

Unfortunately, nope 😟. The method that stops it from crashing seems to make the captures not work for me

I think a better workaround is to change the getter into a function with no parameters.However, I suggest you think long and hard before you propagate errors (via throws) as in your example. When the propagated error is something that can't happen, there's really no point in distorting the entire chain of calls to handle errors, since there's really nothing you can do about them. How (for example) can a utility random number generator fail in a way that isn't a programmer error?I know that proponents of exception handling like to think that if you propagate the exception up to the top level, cleaning up via catch blocks on the way up, the app can continue. But in the case of that kind of error, there's a good argument to say that the app should not be allowed to continue. If the choice is a crash or a future data corruption of potentially unlimited scope, which would the user rather have?[Also, I know it's not your main point, but if you do want to swallow the error as above, it's a crummy idea to us

Hello. How is the SKSpriteNode named ball created? Does it exist at the time the crashing code executes? What does childNodeWithName return if no such node is found? Does it return nil? According to the docs 'childNodeWithName' returns an SKNode? which is either the node or nil if no such node was found. If it is returning nil, then that could be the problem. However, I'm going out on a bit of a limb here because I have no evidence for some of my guesses.I think I would double check that the ball is being created correctly before I arrive in didMoveToView. I'd also be inclined to break that childNodeWithName(BallCategoryName) as! SKSpriteNode into multiple pieces: the first one to find the ball, then make sure it is not nil, then cast it, but cast it in such a way that if it fails to cast it doesn't crash. I think the 'if let...' construction would help a bit with both the nil checking and the casting.

is it upon printing that safari and Mail crash or is it that you are printing from the 2 apps to which then the printing fails?

Still have this problem with the Playground, only difference is that the only output is a warning that the playground have not been able to find the Souces Folderdyld: warning: could not load inserted library '/var/folders/3v/19_tyvk91l7_x9dkrx2xll140000gn/T/com.apple.dt.Xcode.pg/auxiliarymodules/DCB16DFC-2D1D-433D-A4E7-6401B2D83756/Toolbox_Sources.framework/Toolbox_Sources' because image not foundPlayground execution failed: /var/folders/3v/19_tyvk91l7_x9dkrx2xll140000gn/T/./lldb/5291/playground3.swift:1:8: error: no such module 'Toolbox_Sources'import Toolbox_Sources

I think your problem is this line: NSURL *url = [[NSURL URLWithString:UIApplicationOpenSettingsURLString]autorelease];URLWithString will return you an autoreleased URL already, but then you are autoreleasing it again. This will over-release the object. A bigger question here (in all seriousness, I'm not trying to be snide) is why you're not using ARC? At this point in time there's really no reason that you shouldn't be using Automatic Reference Counting. These are exactly the types of crashing bugs that ARC can help prevent. I would strongly encourage you to switch to using ARC for all your code.