file uri scheme

There is an unfortunate behavior when multiple Finder Sync extensions are simultaneously running. If two or more Finder Sync extensions are configured to watch the same folders by setting [FIFinderSyncController defaultController].directoryURLs, then there's a race condition where badges will only be requested ( via requestBadgeIdentifierForURL) and drawn from the extension that started first. Normally, this wouldn't be an issue if extensions are only watching the folders they created, but Dropbox for instance seems to monitor the entire ~/Documents folder (not just their own Dropbox folder), so if the Dropbox Finder Integration extension runs first, no other extension will show its file badges.So what is the expected behavior if two Finder Sync extensions are watching the same folders? There needs to be some intelligent logic to determine which extension gets to show its badges (maybe whoever has registered the folder closest to the actual folder, so whoever is monitoring ~/Documents/MyFolder would

Today while developing a web app, I noticed a 404 error in the console. However, unlike most 404 console errors, it did not show the path to the resource (html file) it was trying to load. Typically, I use this info to instantly determine whether there is a typo in my code or if a resource was not uploaded, etc.Is this by design? Am I missing something?

Greetings,I have an iOS 8 Swift-based app using a UISplitViewController as its root view controller. My project's deployment setting is iOS 8.0 and I had to use launch images (and not a launch storyboard) because launch storyboards did not support containers such as UINavigationController, UISplitViewController and UITabBarController (this is quoted from a DTS response I got).In comes iOS 9 with its iPad multitasking feature, which requires using launch storyboards. Things seem to work (on iOS 9) if I specify my main storyboard as a launch storyboard but iOS 8 displays a black screen during launch. Strangely, if I check the Use as launch screen checkbox for the main storyboard, the compiler spits out an error (Launch screens may not have connections). Using a XIB file (with a UISplitViewController within) as a launch file seems to kind of work on both iOS 8 and iOS 9 but I can't seem to be able to modify the UISplitViewController in IB.This is quite puzzling as there is no way to have the sy

I can't seem to extract RAR files anymore after installing El Capitan. I've tried with several extractor apps in the app store and no luck. Anyone else expiriencing this? Anyone have a solution?Thanks,John

I installed El Capitan today and have noticed an odd problem with available space on the SSD. Before the install the drive had 130GB available but dropped to 82GB after the install. Weird enough but then I trashed a 50GB file and as it was emptying from the trash the available SSD space actually steadily DROPPED to 62GB. Any insights?

NSError has a way to carry additional information around with it: the userInfo dictionary. This includes user-facing information like the localized description, of course, but it also includes tremendously useful details such as underlying errors, particular problem files, etc.ErrorType enums have a way to carry associated data too: values associated with the cases.Is there some way to bridge these two worlds? Obviously the ideal thing would be if Swift synthesized code that automatically mapped associated value tuple fields into userInfo keys, but even if I had to implement a function or computed property to do it myself, that'd be way better than nothing.

ENABLE_TESTABILITY = YESis set to YES in debug, not in release, but if I have a scheme that compiles a release build of my framework (who also build the test target) build will fail with'Module was not compiled for testing' when using @testablein release mode ENABLE-TESTABILITY is set the NOcaused by @testable import inside test target@testable import Awesomekit