LLDB crash

Ken,Thanks a million! That did the trick nicely. For future reference, the lldb command to change how the debugger handles a specific signal isprocess handle <SIGNALNAME> [ --pass <true|false|1|0> ] [ --stop <true|false|1|0> ] [ --notify <true|false|1|0> ]--pass determines if the signal will be passed to the process' signal handler--stop determines if the debugger will stop your process when a signal is received--notify controls whether a message about the signal gets loggedIn my case, the solution was: process handle SIGTERM --stop false --pass true

For what it's worth, my Phone app crashes when I tap the Favorites tab.

I'm in the same boat. It seems that there are quite a few crashes in the OS beta which is understandable. Every once in a while I look down and I see the Apple logo screen like as if it were turning on. Hopefully in the next few weeks the betas will be able to solve those problems and give us all day battery life again. I guess thats what we get for wanting to develop for the watchOS 2 😝

this did not work for me. I was able to open the phone app and listen to the VM then it promptly crashed and continues to crash. I tried eaving the voicemail unread and that didn't help either.

I'm having this exact issue on beta 2. Apps fail to update. Trying to Update All or Update each app individually leads to the App Store prompting me for my password. I enter it and it asks for it again and again. If I navigate to the homescreen, there is a blue dot next to the specific apps (indicating they're updated), but when I tap to launch it, the app will immediately crash. Restarting my iPhone allows for me to use the older version of the app again.However, the only way I can update apps right now is uninstalling the app and reinstalling the latest version from the App Store. Will try to make a report of this ASAP! :-)

Interestingly enough, my Phone app doesn't crash. It just won't stay in the foreground. I can seeing it running in the apps list. And, no crash log is created.Make sure you're submitting bug reports for this type of thing. Just grumbling here doesn't help get it fixed.

So the voicemail fix worked it looks like it's the favorites tab causing the app to crash

You make a reasonable point, but I think there is value in making a distinction because there is already an exception handling mechanism in our (Xcode) ecosystem, perhaps two, if you count the Obj-C and C++ exception mechanisms separately, and Swift is unaware of both of them.I think there are three key differences between Swift error handling and exceptions in the other languages:1. In Swift, 'throw' is a transfer of control to the calling function, similar a 'return'. Elsewhere, it's a transfer of control to somewhere else in the stack.2. In the other languages, a function that isn't exception-aware can have a transfer of control across it (from below it to above it). In Swift, a non-exception-aware function blocks any error handling control transfer.3. Swift has no system (program failure) exceptions, such as invalid argument or nil pointer that are fed into the error handling mechanism. Those sorts of failures immediately and correctly cause a crash. Actual errors appear only by API contract betw

It sounds like you're misunderstanding There's no documented API for that for not possible.The nice people from Apple won't tell you about API that aren't documented, and your fellow developers all get to write We told you so when your application uses an undocumented API that breaks, stops working, or randomly crashes your application.After all, there's probably at least one method involving a kernel debugger that would let you generate any event you could possibly want to, if you had access to all of the required information. But that's not going to be a documented, or supported, way of doing so.

Yes, same for me. OK with first Beta but crashes on startup with second Beta.I tried OS X Recovery to reinstall El Capitan, and it succesfully reinstalled the first Beta. FCPX then worked again.I 'upgraded' to Beta 2 and then it crashed again.

Gregstus, It is really difficult to give non-trivial help on a forum. Forums are really best for short answers to specific questions. Now, even though you have a specific question (why does this line crash?) and the answer turns out also to be specific (because the node doesn't exist or can't be cast to that type), it does require the context of both how SpriteKit works and how Swift works to understand why that answer answers that question! Unfortunately, I (and I assume the others trying to help) just haven't got the time/knowledge/ability/desire (delete as appropriate) to provide the necessary background and context in Swift and SpriteKit to explain how and why that answer answers that question. In order for our answers to make sense, that context has to exist.The way to get that context is by finding some write-ups and tutorials and example apps and studying them. Apple documentation and Sample Apps are one source, and there are many many tutorials on the web. Although I have quite a bit of progr