It is strange that nothing is showing in the console logs. On my Sequoia Mac the plugin is working, but I am reading on the Apple Developer forums that there are some issues with using FinderSync extensions on Sequoiaā¦
Hi @matt.nye,
It is bizarre that you arenāt seeing anything in the console. There should be quite a few lines showing-up there, regardless of what the result of the commands are.
Can you copy and paste the output from the terminal here?
What if you just search for odrive instead of Process:FinderSyncExtension in the console? You can exit odrive to reduce noise when filter by āodriveā.
The extension is being installed, since it comes back in the list after adding it with pluginkit. It seems like it is not being enabled, though, and there isnāt any information coming back to tell us why. What makes it more difficult is that it is working correctly on the two machines running 10.15 that Iāve tested here.
Maybe there is a conflict of some sort? I see that @kenlefeb looks to have some other Finder extensions loaded. @matt.nye do you also have some other Finder extensions loaded?
@matt.nye since your console shows 389 messages for the odrive filter, there could be some info there that could point us in the right direction.
Was this after exiting odrive? If not, can you exit odrive and run the commands again?
In either case can you please copy and paste the console entries into a txt file and send that over to me? You can message me directly with it, if you like. Just click on my name and then click on āMessageā.
Do you know, Tony, if thereās a way to temporarily disable my other extensions (without having to uninstall all of the apps they came with) to see if that fixes our problem with the ODrive extension?
Also, is there any way to manually unsync items without using the Finder extension? I would be happy using a workaround until long-term solutions are discovered.
Hi @matt.nye and @kenlefeb,
This is a bit of a shot in the dark, but I wanted to try something.
This command sequence will copy the odriveapp.app file into the userās Applications folder and then go through the extension registration. My thinking is that the new version of MacOS may be picky about where the extension is locatedā¦