> On Nov 28, 2016, at 7:42 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On Nov 28, 2016, at 17:30 , Charles Srstka <cocoa...@charlessoft.com > <mailto:cocoa...@charlessoft.com>> wrote: >> >> This is currently broken in Swift, as of Swift 3, where all file reference >> URLs will get silently and unceremoniously converted back to path-based ones >> at the bridge. > > NSURL or URL or both?
.fileReferenceURL doesn’t exist on URL. It does exist on NSURL, but thanks to the bridging magic it returns a URL, which the ObjC-Swift bridge turns into a normal file path URL. Unfortunately, the second comment on this thread: https://bugs.swift.org/browse/SR-2728 <https://bugs.swift.org/browse/SR-2728> indicates that this might have been intentional behavior. :-/ Charles _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
