The context menu (Finder Extension) is gone in the latest version of odrive+MacOSX (v4871 and 10.11.3).
In previous versions, as you know, when I right-click the files in odrive folder, I could see the context menu (Finder Extension) “Sync” “Unsync” etc., but now the menu is not displayed.
I suspect that the Finder extension is not installed properly; I checked “Extensions preferences” in MacOSX System Preferences, and I do not see any Finder Extensions.
Hi @Misho,
Let’s try a manual install and see what happens. Please make sure you have the latest version installed (4894 as of this post)
Exit odrive
Open up a terminal
enter the following and then hit enter:
pluginkit -vmA | grep odrive Is anything show at this point?
enter the following and then hit enter:
pluginkit -r ~/.odrive/bin/4894/odriveapp.app/Contents/PlugIns/* this will remove the extension, if it is installed
enter the following and then hit enter:
pluginkit -vmA | grep odrive nothing should be listed after running this command
enter the following and then hit enter:
pluginkit -a ~/.odrive/bin/4894/odriveapp.app/Contents/PlugIns/* This will install the extension
enter the following and then hit enter:
pluginkit -vmA | grep odrive This should now show that the odrive extension is installed and it should be visible in the extensions listing
Here is a video going through the process, just to make sure the steps and results are clear. Ignore the fact that the directories I’m tying in are slightly different, it was created a little while ago
The problem is solved; the actual problem was the other lines in system.log, which was
kernel[0]: Sandbox: coresymbolicatio(39999) System Policy: deny(1) file-write-create /System/Library/Caches/com.apple.coresymbolicationd
coresymbolicationd[39999]: /System/Library/Caches/com.apple.coresymbolicationd/data does not exist, resetting cache
coresymbolicationd[39999]: Attempt to create [/System/Library/Caches/com.apple.coresymbolicationd/data] failed. No such file or directory
coresymbolicationd[39999]: Unable to open storage at /System/Library/Caches/com.apple.coresymbolicationd/data
This was a known problem, and I could solve this issue by the solution post there.
I have to left /System/Library/Caches as norestricted, but I don’t mind.
After I solved this issue, the context menu appears, odrive-plugin can be found in SystemPreferences, and no log lines like plug-in sdk "com.apple.FinderSync" not registered are written.
I for your information drop the output of your instruction. This output is BEFORE fixing the above problem, but even AFTER I fixed the problem, I can get the same output.
$ pluginkit -r ~/.odrive/bin/4894/odriveapp.app/Contents/PlugIns/*
remove: no plugin at /Users/misho/.odrive/bin/4894/odriveapp.app/Contents/PlugIns/FinderSyncExtension.appex
$ pluginkit -vmA | grep odrive
$ pluginkit -a ~/.odrive/bin/4894/odriveapp.app/Contents/PlugIns/*
Hi Tony,
I have recently installed odrive 5039 and have no context menu. I’m using OSX 10.11.3
Went through your instruction of manual installation but it didn’t help. Here is what I did:
> MacBook-Pro-Lukasz:~ lukasz$ pluginkit -vmA | grep odrive
K let’s try the steps for performing a manual install and see what happens:
Exit odrive
Open up a terminal
enter the following and then hit enter: pluginkit -vmA | grep odrive
Is anything showing at this point?
enter the following and then hit enter: pluginkit -r ~/.odrive/bin/5174/odriveapp.app/Contents/PlugIns/*
this will remove the extension, if it is installed
enter the following and then hit enter: pluginkit -vmA | grep odrive
nothing should be listed after running this command
enter the following and then hit enter: pluginkit -a ~/.odrive/bin/5174/odriveapp.app/Contents/PlugIns/*
This will install the extension
enter the following and then hit enter: pluginkit -vmA | grep odrive
This should now show that the odrive extension is installed and it should be visible in the extensions listing
Here is a video going through the process, just to make sure the steps and results are clear. Ignore the fact that the directories I’m typing in are slightly different, it was created a little while ago: Amazon Drive
Keep an eye on the console, too, for any odd errors, like the ones cited here: