openradar-mirror
openradar-mirror copied to clipboard
32839314: Class FIFinderSyncExtensionHost implemented twice
Description
Area:
Finder
Summary:
On some project, I get this warning in the Xcode console when presenting an open panel:
objc[80401]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/FinderKit (0x10d099200) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x115309c00). One of the two will be used. Which one is undefined.
Steps to Reproduce:
I'm not really sure what triggers this warning, as it does not show when I try to reproduce the issue on an empty project.
Anyway, here's the open-panel code:
NSOpenPanel * panel;
panel = [ NSOpenPanel openPanel ];
panel.canChooseFiles = NO;
panel.canChooseDirectories = YES;
panel.canCreateDirectories = YES;
panel.canSelectHiddenExtension = YES;
panel.showsHiddenFiles = NO;
panel.treatsFilePackagesAsDirectories = NO;
panel.allowsMultipleSelection = NO;
[ panel beginSheetModalForWindow: self.view.window completionHandler: ^( NSInteger res )
{
( void )res;
}
];
Warning is shown after the call to beginSheetModalForWindow:completionHandler:
Expected Results:
Presenting an open-panel shouldn't trigger any warning.
Observed Results:
Warning about FIFinderSyncExtensionHost class is sometimes shown.
Version:
Xcode Version 9.0 beta (9M136h) macOS Version 10.13 Beta (17A264c)
Product Version: Created: 2017-06-18T14:40:51.281930 Originated: 2017-06-18T16:38:00 Open Radar Link: http://www.openradar.me/32839314
same
same issue with macvim, error message displayed when opening multi tabs
I have the same problem when I call [openDlg runModal] in XCode 9. So who know why?
Same issue. The error message would appear if I create a new file and run module (F5) before saving it. A pop-up window would then appear for me to save the file to a path and after that this message would be in the Terminal window already. Only appears once though. Similar actions would not trigger the message from 2nd time on.
Anyone has figured out the reason?
objc[68786]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/FinderKit (0x12a480b68) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x12e3cbcd8). One of the two will be used. Which one is undefined.
same issue as @DodoxGit , same message. I see it when I launch git-scm's git gui client.
I get this regularly when using Native File Dialogs
It happens whenever I use an open dialog (single or multiple)
I have the same issue here when i use PyQt5 FileDialog class. i saw that a lot of people are facing the same problem on mac os sierra and high sierra, it's related to the OS, so anything that calls or uses the native os x File System browser generates this conflict. Hope that it gets fixed !
Special use case is if we open the panel when Command Key pressed until we double click on file to be opened. This was causing crash on OSX 10.11.5 when we call runModel on NSOpenPanel i fix it by calling like this,
[openPanel beginWithCompletionHandler:^(NSModalResponse result) {
if (result == NSFileHandlingPanelOKButton)
{
[self openImageWithURL:[openPanel URL]];
}
}];
Instead of
NSUInteger result = [openPanel runModal];
if (result == NSFileHandlingPanelOKButton)
{
[self openImageWithURL:[panel URL]];
}
Cheers.
I get the same issue. As someone pointed out it seems to only occur when using Native file system dialogs.
So the warning goes away if you do this:
options = QFileDialog.Options()
options |= QFileDialog.DontUseNativeDialog
I'm using Mac OS X 10.14.2 (Mojave)
I get this when running the Java Swing-based project WyldCard (https://github.com/defano/wyldcard), output to terminal when I perform the "Open Stack" command. This in turn executes the Swing method FileDialog(). It only seems to happen on the first invocation.
Simply running:
osascript -e 'choose file'
Produces the same issue for me. Hints pretty strongly at this being unfixable.