Request failed with http status code 503

With Xcode 6.3.2 and Swift 1.3 Collada (DAE) files were loaded and entries found (e.g. animation) by using SCNSceneSource.entryWithIdentifier. With Xcode 7.0 and Swift 2.0, the file is loaded (SCNSceneSource.identifiersOfEntriesWithClass work) but no entries are found.Tried with MacOSX, iOS apps and several files.Her is the codelet sceneSource = SCNSceneSource(URL: url!, options: nil) let animationIDs = sceneSource.identifiersOfEntriesWithClass(CAAnimation.self) as [String] let animation : CAAnimation? = sceneSource.entryWithIdentifier(Name, withClass: CAAnimation.self)First two lines work and return identifiers including the one label Name. Line 3 returns only nil. Same code worked before with Xcode 6.3.2 and Swift 1.3

HelloFor weeks I've been getting a kernal panic almost every day sometimes multiple times/day. Other times my entire mahcine (Retina macbook pro) will freeze up and not recover. Any suggestions on how to fix it would be great. Below is the latest console kernal panic.*** Panic Report ***panic(cpu 2 caller 0xffffff8003c17cc2): Kernel trap at 0xffffff800390e27e, type 14=page fault, registers:CR0: 0x0000000080010033, CR2: 0xffffff84f13fad24, CR3: 0x00000003804bb029, CR4: 0x00000000001626e0RAX: 0x00000000b0d56031, RBX: 0xffffff81a32cb400, RCX: 0xffffff81a32cb800, RDX: 0x0103000002030001RSP: 0xffffff82606d3bc0, RBP: 0xffffff82606d3c30, RSI: 0xffffff81a32cb000, RDI: 0x000000008ac04080R8: 0xffffff85f6ff6d64, R9: 0xffffff84f13fad24, R10: 0xffffff82b8aa6dec, R11: 0xffffff81a32cb800R12: 0xfffffe8b54c1a000, R13: 0xffffff81a32cbffe, R14: 0xffffff8027433120, R15: 0x000000001600e6b7RFL: 0x0000000000010202, RIP: 0xffffff800390e27e, CS: 0x0000000000000008, SS: 0x0000000000000000Fault CR2: 0xffffff84f13fad24, Error code

Up until now I've been using -[NSValue valueWithPointer:] to store the addresses of selectors in an array. Sometimes I want to store the lack of a selector so have been using [NSValue valueWithPointer:NULL]. In the 10.11 SDK this now gives a Null passed to a callee that requires a non-null argument warning.So is the header for NSValue wrong in saying it requires a non-null argument, or should I update my code to maybe use an NSNull instead (which is a bit of a pain when it comes to unwrapping, but not hard).BTW - valeWithPointer is quite happy to create a value with null and correctly gets round-tripped when calling [NSValue pointerValue] on it (i,e it comes back as NULL.

Using El Capitan and XCode 7, the following trivial snippet of code causes a Swift related exception to be thrown:func openDocument(sender: AnyObject?) { let panel = NSOpenPanel(); let types = [ abc, def ] panel.allowedFileTypes = types; panel.runModal(); }The exception is [Swift._SwiftDeferredNSArray supportsSecureCoding]: unrecognized selector sent to class 0x1002de2c0. And it is triggered when assigning types to allowedFileTypes.

Just started building my app with 10.11 SDK and am getting a lot of warnings on classes where I have explicitly set NS_DESIGNATED_INITIALIZER where init is not one of them.E.g@interface MCChecksumAccumulator : NSObjecttypedef NS_OPTIONS(NSInteger, MCWantedChecksums){........};/- (instancetype)initWithWantedChecksums:(MCWantedChecksums)wanted NS_DESIGNATED_INITIALIZER;@end@implementation MCChecksumAccumulator <<<< Method override for the designated initializer of the superclass '-init' not found- (instancetype)initWithWantedChecksums:(MCWantedChecksums)wanted{...}@endIf I remove the NS_DESIGNATED_INITIALIZER from initWithWantedChecksums: then the warning goes away. But I've done this explicitly to prevent people trying to use init on this class directly.Looking at NSObject I see:- (instancetype)init#if NS_ENFORCE_NSOBJECT_DESIGNATED_INITIALIZER NS_DESIGNATED_INITIALIZER#endif ;and NS_ENFORCE_NSOBJECT_DESIGNATED_INITIALIZER is declared as:/ NS_ENFORCE_NSOBJECT_DESIGNATED_INITIALIZER == 1* marks -[NS

I am developing a keyboard extension. Even when it's allowed full access, there are still some cases it disappears and the default iPhone keyboard appears insted. I'm not talking about the password and phone number fields.The first case is the 'Search iPhone' field. There are some custom keyboards that appear there. However, my keyboard is not listed among the available keyboards for that field.The second case is a bit strange: if a device is not passcode protected, locking the screen with open keyboard and unlocking it does nothing, i.e. the keyboard still appears on the screen and everything is fine. However, if a device is passcode protected, after unlocking it, my keyboard is replaced with the system default. The interesting thing is that the same custom keyboards that can be used in the 'Search iPhone' field, remain active after unlocking a passcode protected device.I believe, there should be some setting or property in the plist file or something. I just cant find anything about it.The other thing that