show when run

OS X is nice because its easy to setup and run and cheap! Never had any issues with it here. I'm still running 10.6.8 on my servers for everything and still running strong so far! I just worry about a drive or other hardware giving out at this point.Anything MS to me is a nightmare. They make things more difficult to setup than nessassary and the technet articles give a whole story and give examples how it should be setup but don't really tell you how to do it. Then half the time its wrong in my experiances. Our MS fanboi is trying to setup the latest version of System Center and is having fun with that and getting it to work and hasn't been too happy. I skimmed over the documentation and noticed it even supports OS X, but Munki can do most of what it can so I have no use for it. Along with with Endpoint Antivirus, but again its lacking in any management on the OS X side so dissappointed.With Netboot, Caching, basic file serving, and profile manager I still think OS X server is liab

You can do this in Xcode:(An embedded screen shot should appear here)The embedded graphic doesn't seem to appear when the post is saved.In Xcode:Debug/Debug Workflow/Always Show Disassembly

Once Apple decides it's ready. Typically some time after Beta 1 and before Beta 3 😁History teaches us on average a couple weeks after the initial beta release. You're not running Beta 1 on your primary device are you?

wjens wrote:> I thought the XPC Service template within xcode was only for XPC Services hosted within a parent application - produces .xpc files. I'm pretty sure those don't work as standalone XPC services like you describe above.Thanks for your input.I thought that this might be the case as well. In a variant of my prior test code, not shown here, I tried it with an Launch Agent based on the .app AppKit template but this didn't really change the broken connection behaviour. Which leads me to believe it's some kind of configuration issue.Although, I haven't tried the code of the Launch Agent, as posted above, as an Mac App created with the .app AppKit Xcode template but with the GUI stuff stripped out or with the Command Line Tool template.I forgot to mention in my previous post that debugging print statements in the Launch Agent's main.m, like the fprintf() calls in the example code or NSLog() or asl_log() calls in my original test code, do not appear anywhere in the command line output or in the System C

I don't have any suggestions, but just FYI...I am also running 10.10.3 and XCode 7 beta (7A120f), and I downloaded the Swift Standard Library playground sample and it seems to work fine (although it did take some time to compile and run each page as I switched between them).So the problem isn't just specifically being on 10.10.3.

Interesting, the rest of your question showed up, I think I see your problem.You are doing the cast as in my first suggestion, but you are passing the non-casted parameter (paramIn) to the function instead of the new casted version (param)

Ufortunatley the watchOS 2 needs your phone to be running iOS 9. So without your device going back to 8... it will not pair.