“translate scheme”

Thanks for pointing me to the right direction. I could solve my issue now.For all developers having the same issue, the solution is to add a whitelist of all URL schemes your App may need to call into the Info.plist. The key to add is LSApplicationQueriesSchemes and its value is an array with all the URL schemes.Of course this still kills many Apps which offer services to other Apps via X-callback-URL protocol, but at least this will work for many other Apps.

Right. You'll have to declare the URL schemes, you want to use in your Info.plist. Use the key LSApplicationQueriesSchemes for that.Note: Apps that were built before iOS 9 will always return NO for canOpenURL as soon as they checked 50 different schemes. Even rebooting the device doesn't reset those!There will also be session 509 about the new Universal Links called Seamless Linking to Your App on Thursday.

Hi,I found it complicated to get the complications to show up in the Simulator—the code was relatively simple, but placeholders didn’t seem to show up due to caching issues.The video ‘Creating Complications with ClockKit’ is definitely the best place to start—the code below is based on the code shown in the video.Create a new project------------------------------------------I found it easier to create a new project with the complication support added in (which also generates the stubs for the data source protocol functions), and then add that to my existing project. + File > New > Project > watchOS > Application (‘iOS App with WatchKit App’) + Add in ‘Include Complication’Targets------------------------------------------Check the following settings for the WatchKit Extension target: + Target > WatchKit Extension + Complications Configuration: + Data Source Class = %(PRODUCT_MODULE_NAME).ComplicationController + Supported Families: check required families (only check the ones you’re handling in

solved by making sure the framewok scheme tests target has only Test checked in and no Run

El Capitan provides a new class method on NSError named +[NSError setUserInfoValueProviderForDomain:provider:] which allows you to decouple the code for constructing userInfo dictionaries from your worker code. Since you cast an ErrorType to an NSError when you send it to APIs like -[NSApp presentError:], I'd expect that this would work with ErrorTypes as well. It's pretty elegant, actually; your worker code can only have the bare minimum needed to mark an error (throw MyErrorEnum.NuclearWar), and the code to translate that into Sorry, you have unleashed the apocalypse, and now the living envy the dead. can be somewhere else.