file uri scheme

That's an interesting issue and there currently is no built-in mechanuism to automatically handle it. I'd suggest filing an enhancement request.In the meanwhile, you'll need to listen for the trait collection changes and rework your toolbar layout in response. I'd suggest moving the excess buttons into a popover, while is presented from a More button, when in the compact environment.

i placed a wkinterfacemovie in storyboard and set an outlet to the interface file, this worked for me in willActivate():let url = NSBundle.mainBundle().URLForResource(song, withExtension: mp3)myMoviePlayer.setMovieURL(url!)

Do you have sufficient constraints to specify the horizontal and vertical size and position of all your views? For first, for example, I don't see anything specifying horizontal position. Or inside either for that matter. And I don't see any constraints at all on the view you're attempting to add as a subview of your builder UIView. Are there auto layout warnings in the console output?The only thing the XIB loading does is instantiate subviews and connect up any outlets (assuming you have the File's Owner and outlets set up properly). The positioning and sizing of the view is up to the superview.

Replying to myself,If I init the node just as above and instead of running the action SKAction.play() I run the action SKAction.playSoundFileNamed(, waitForCompletion: false) i.e. leaving the name of the sound file empty it works. At least plays the sound. Have yet to test if it actually does the 3D effects.

While there is no there is no “realtime tap” currently in AVAudioEngine, one way you may want to go about tacking this is by writing your own effect v3 AudioUnit (Audio Unit Extensions) and then inserting that into the engine.The idea would be to create and publish the AudioUnit as an effect, then create an instance of it in AVAudioEngine using a new iOS 9 AVAudioUnit method:+ (void)instantiateWithComponentDescription:(AudioComponentDescription)audioComponentDescription options:(AudioComponentInstantiationOptions)options completionHandler:(void (^)(__kindof AVAudioUnit * __nullable audioUnit, NSError * __nullable error))completionHandler NS_AVAILABLE(10_11, 9_0);Of course this is more work than just having an AVAudioEngine provided realtime processing tap, so please file an enhancement request for that feature https://bugreport.apple.com/Audio Unit Extensions were discussed at WWDC 2015 and are going to provide a very powerful way to to extend audio processing on iOS 9 (AU components have of course b

yes, all of the WCSession APIs are intended to work for seed 1. Please file a bug with a sample project if you are finding otherwise 🙂

I see your point - might be time to file a bug against that linking.

Glad I read this, I too am noticing that the workout session is not keeping my app in the foreground. Good to know it's not just me. I will file a bug report for this.

It's a travesty on the whole. Some sort of background operation is chewing through CPU cycles, causing everything from an iPad to an iphone 6 (and Plus) to burn through battery in less than half a day. Sometimes it's drained an iPad Air 2 we have for testing within 3 hours from a full charge with zero on-time. Meaning, the device was in standby for 3 hours from a full charge then basically dead.Beyond this obvious battery problem is another of great concern regarding iCloud backups. MASSIVE storage loss on our iCloud accounts for test devices. One account has over 500 GB of the entire 1 TB available allocated to Backups and yet when you actually look at the list of backups there are only two devices with less than 20 GB in size each. Where is the rest of the storage going? More transparency for iCloud relative to backups should be made available especially when this is crippling development. We can't do anything to delete the data and have no eta on when this will be resolved, or if it will impact any pre-exi

Can you explain little more? What I see now when creating new .h and .m files for example tableviewcontroller it's no longer created inside the application folder but rather at the top of the list and can't move then inside. This is little weird.

Here are some XCTest style assertions I wrote for checking for thrown Swift errors. Hopefully by the time Xcode 7 is final, there will be built-in versions of these.// // XCTAssertSwiftError.swift // // Created by LCS on 6/17/15. // Released into public domain; use at your own risk. // import XCTest func XCTempAssertThrowsError(message: String = , file: String = __FILE__, line: UInt = __LINE__, _ block: () throws -> ()) { do { try block() let msg = (message == ) ? Tested block did not throw error as expected. : message XCTFail(msg, file: file, line: line) } catch {} } func XCTempAssertThrowsSpecificError(kind: ErrorType, _ message: String = , file: String = __FILE__, line: UInt = __LINE__, _ block: () throws -> ()) { do { try block() let msg = (message == ) ? Tested block did not throw expected (kind) error. : message XCTFail(msg, file: file, line: line) } catch let error as NSError { let expected = kind as NSError if ((error.domain != expected.domai