dsym file

Hi,After upgrading from Yosemite to El Capitan Beta, I tried to edit in /System/Library/LaunchDaemons/ssh.plist to change the default SSH port to a custom one. This is the process I've been using for a couple of years.The problem is that El Capitan doesn't allow me to change anything in this folder (not even with sudo). The folder and its files are marked as restricted' when I list the contents with ls -lO. The same folder listing in previous versions of OS X does not show restricted.Is this something new to OS X El Capitan? How can I edit files/folders that are restricted?Regards,Spencer

Hi, I'm using Xcode6 and created a test app for ipad. It compiles and runs fine in simulator. My next step is to distribute it using adhoc distribution mechanism. Here is what I've done1. Using Keychain Access to create a public/private key pair.2. Load it up into Developer Center to create a certificate, then download it.3. Add my ipad UUID under Devices.4. Create a adhoc provisioning profile by including my ipad in it, I only have one device in Member Center. Let's call the provision MyProv.5. Run the .cer file by double clicking it.6. Download the .mobileprovision file from Member Center to desktop. Then double click it.Now, in Xcode, under Build Setting, I change Provisioning Profile Debug and Release entry to point to MyProv, then run Product->Archive. When archiving the app, Xcode as me if I want to use my key created in step 1 above to sign the bundle. I allow it. I also choose to Save for ad hoc distribution when asked. In the summary page, I can see the Provisioning Profile colum

I'm kind of dissapointed with the lack of optional protocols for native Swift types still in 2.0. I am happy to see the workaround of declaring default implementations through protocol extensions, but this seems like a workaround rather then a solution. The language natively supports optional protocols, except they have to be delared with the @objc keyword, which rules out using classes/structs/enums that I define in in the function declaration. I tried using the @nonobjc keyword inside the protocol, but only ended up with a compiler error (which is what I was expecting anyway). I'm sure there is a valid reason not to implement them in the language, I just don't know what it is, and can't for the life of me figure it out on my own. Especially as all the language support for working with them seems to be in place.AndrewPS, In case you're wondering, yes I filed a bug report on this a long time ago.

First of all, let me just go out and say that this new error handling system in Swift is a huge, huge improvement. However, this is one case that I'm unsure about, which is when you legitimately care about errors. However, sometimes you don't care about the specific error, but you just want to know if something succeeds or not. A good example is checking the availability of a file, where you just want to know if it's reachable and don't want to bomb out if it's not. In Objective-C, this would be done with one line of code, simply by passing NULL for the error parameter:BOOL isReachable = [someURL.checkResourceIsReachableAndReturnError: NULL];However, in Swift 2, the best way I can see to do this is:let someURL = ... let isReachable: Bool do { try someURL.checkResourceIsReachableAndReturnError() isReachable = true } catch { isReachable = false }This seems somewhat verbose and awkward. Is there any more elegant way just to check if a file is reachable without treating the result as an error?

I am using a custom embedded framework to make my watch extension currently work. However, when I use Xcode 7 with watchOS 2, I get a bunch of warnings, one of which offers to Update to recommended settings. Has anyone else gotten this?When I click Perform changes to update to the recommended settings, all the lines #import <MyFramework/MyFramework.h> in my watch extension interface controller files say file not found. I have checked to make sure that I am linking with the library MyFramework in the app extension, but this error still appears. Again, I wasn't having this issue prior to Xcode 7.Any help would be greatly appreciated. Thanks!Edit: I tried creating a brand new project with an Apple Watch app+extension. I created a custom framework and linked to it in my watch extension, but this error still shows up. So I don't think it has to do with the recommended settings...

File menu no longer shows option to create snapshot. But project window still refers to snapshots.

I am looking for a good 32/64 bit version of a zip library for compressing directories to password protected files. Most of the ones I find (for example zipArchive) are fairly old and 32 bit based.