You can try to clean up once again. Perhaps in the last time the âdomainsâ are not removed yet. This time you can check them manually before rebooting.
If it still doesnât work, could you send your logs to support@seafile.com?
Exciting. Looking forward to this - let us know if thereâs anything we can do to help! We know at least one user is custom compiling it with little effort, but I suppose you will want to have a universal binary. Donât be afraid to have an Apple ARM and Apple Intel version separate, though!
Not sure if this is a bug or something the Apple FileProvider API causes: in previous SeaDrive Versions we could simply drag and drop something from the SeaDrive Directory to (for example) Desktop and because it was seen as a different drive, it would automatically copy the files / folders.
When i Drag and Drop something now, it moves it and deletes it from the Server.
I guess this is because the new SeaDrive Sync Folder is located in ~/Library/CloudStorage and not recognized as âexternalâ storage?
Maybe this can be solved in your Software?
And second thing - the spacebar preview feature still does not work, but in previous versions (2.x) it worked (it started streaming the file in preview from the server).
Hello, the file or directory behavior in Fileprovider is consistent with that of mac system. The move operation will move the file without copying. If you want to copy, you can use the copy operation. Seadrive 3.0 only supports the thumbnail of images, is your preview a image?
Hello, it seems that your mac os canât create a file provider, this may be a problem with the current system. Do you use seadrive 3.0.1 and do you remove the metadata under~/Library/Containers/com.seafile.seadrive.fprovider/Data/Documents/*?
Unfortunately doesnât work on my M1 Max Pro laptop.
After rebooting, and doing a fresh install, I was able to log in successfully using SeaDrive and got a green tick on the SeaDrive app in the menubar. I then went to encrypted libraries and entered in one of my encrypted libraries. However, from there it did not work. I get this error message:
[03/13/23 09:39:55] failed to send rpc call: Broken pipe
[03/13/23 09:39:55] failed to get global sync status: Transport Error
[03/13/23 09:39:55] failed to send rpc call: Broken pipe
[03/13/23 09:39:55] failed to get sync errors: Transport Error
[03/13/23 09:39:56] failed to send rpc call: Broken pipe
[03/13/23 09:39:56] failed to get seadrive.events: Transport Error
[03/13/23 09:39:56] failed to send rpc call: Broken pipe
[03/13/23 09:39:56] failed to get sync notification: Transport Error
[03/13/23 09:39:56] failed to send rpc call: Broken pipe
[03/13/23 09:39:56] failed to get global sync status: Transport Error
[03/13/23 09:39:56] failed to send rpc call: Broken pipe
[03/13/23 09:39:56] failed to get sync errors: Transport Error
[03/13/23 09:39:57] failed to send rpc call: Broken pipe
[03/13/23 09:39:57] failed to get seadrive.events: Transport Error
That error message repeats non stop.
So then I rebooted again, and now I get this error message:
[03/13/23 09:42:34] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:36] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:38] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:40] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:42] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:44] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:46] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:48] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:50] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:52] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:54] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:56] pipe client failed to connect to server: Connection refused
[03/13/23 09:42:58] pipe client failed to connect to server: Connection refused
[03/13/23 09:43:00] pipe client failed to connect to server: Connection refused
[03/13/23 09:43:02] pipe client failed to connect to server: Connection refused
[03/13/23 09:43:04] pipe client failed to connect to server: Connection refused
So still doesnât work from me. Again, I did exactly evert single step you mentioned in your OP, starting with this:
Remove all accounts from SeaDrive 3.0.0. Wait until the virtual drive disappears from Finder.
Exit SeaDrive.
run rm -rf ~/Library/Containers/com.seafile.seadrive.fprovider/Data/Documents/* to clean up existing metadata.
Reboot your computer.
Then I did this:
Then run fileproviderctl domain remove <domain id>, where is the ID in red square.
Still no luck. I rebooted again and thatâs when I got the second error message in the log file again
Hello, these errors should be caused by the seadrive extension not starting. You can click SeaDrive in the sidebar of finder, and the system will launch the seadrive extension.
Hello, you can exit seadrive first, then click the entry in the finder, and then restart seadrive to try. In addition, you can check whether there is a crash report related to seadrive. Thanks a lot.