SeaDrive for macOS 3.0.1 Beta is available for testing

Jonathan · February 10, 2023, 6:05am

Hi everyone,

Thank you for the feedbacks to SeaDrive 3.0.0 version. 3.0.1 version is now available for testing.

Improvements included:

Fix some bugs that can cause crashes.
File locking (automatic lock is infeasible, though)
Photo preview
Add events.log
Minor bug fixes

You can download it from https://download.seafile.com/f/c9d5827fe354488ea7f7/?dl=1

Due to some breaking changes to metadata created by 3.0.0 version, you have to follow these steps before upgrading from 3.0.0 version:

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.

If 3.0.1 still can’t work, you may check whether the old “domains” are removed successfully.

Run fileproviderctl domain list command from command line. You should see output like below.

Then run fileproviderctl domain remove <domain id>, where is the ID in red square.

drmartin · February 10, 2023, 7:14am

Thanks for the great work on MacOS. How’s the timeline coming for Apple Silicon ARM support for SeaDrive and sync clients?

vootoo · February 10, 2023, 3:13pm

thanks for the updating,when will you release the RC version.

Blackbelt-Ninja · February 11, 2023, 4:55pm

Hey, I mean - come on… still not fixed… ?

No Apple Silicon Binary… still only Intel? Even dropbox finally delivered an apple silicon version of the client.

It’s not usable… seafiles advantages to the competition are melting… ( maybe not existing anymore )

Jonathan · February 12, 2023, 7:53am

It’s a problem caused by existing metadata. You need to follow this steps to remove it first.

We’ll look into providing native Apple Silicon support this year.

Blackbelt-Ninja · February 12, 2023, 9:50am

I already did, as suggested in your first post. Also rebooted… before I installed ne ne 3.0.1 “beta”

Jonathan · February 13, 2023, 7:23am

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?

drmartin · February 17, 2023, 11:21am

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!

philipz794 · February 17, 2023, 12:28pm

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).

moobyfr · February 24, 2023, 5:35am

For me, this version does not work.
I verified, I have no fileprovider registered:

➜  ~ fileproviderctl domain list
 - iCloud Drive (hidden)
	com.apple.CloudDocs.MobileDocumentsFileProvider
	~/L{5}y/M{14}s

But I get this error after adding a account:

[02/24/23 06:16:18] [File Provider] Listing domains
[02/24/23 06:16:18] [File Provider] Adding domain "b14c94e1fb1c36857bccde918fc789e1" "Emmanuel Blindauer(seafile.unistra.fr)"
[02/24/23 06:16:18] [File Provider] Error adding domain: Error Domain=NSCocoaErrorDomain Code=260 "Le dossier « B4404F8F-C28F-41F6-9C0A-7CB12A8E38DA » n’existe pas." UserInfo={NSFilePath=/Users/e.blindauer/Library/Application Support/FileProvider/B4404F8F-C28F-41F6-9C0A-7CB12A8E38DA, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x600002a32f40 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
[02/24/23 06:16:18] [File Provider] Listing domains

feiniks · February 28, 2023, 7:31am

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?

feiniks · February 28, 2023, 7:35am

Hello, what mac version are you using? Please make sure you use a version above mac11.

moobyfr · February 28, 2023, 5:46pm

it’s a 13.2.1 (22D68). IIRC I was on 13.1 or 13.2 before and the same problem was present.

feiniks · March 2, 2023, 9:00am

Hello, can you list the contents under the directory /Users/e.blindauer/Library/Application Support/FileProvider ?

moobyfr · March 4, 2023, 6:26am

➜  ~ ls -la "/Users/e.blindauer/Library/Application Support/FileProvider/"
total 0
drwxr-xr-x    3 e.blindauer  staff    96 16 fév 12:11 .
drwx------+ 190 e.blindauer  staff  6080 28 fév 18:52 ..
drwxr-xr-x    2 e.blindauer  staff    64 16 fév 12:11 2A1CA581-4B0D-4DCA-92EE-69228A79CC90
➜  ~ ls -la "/Users/e.blindauer/Library/Application Support/FileProvider/2A1CA581-4B0D-4DCA-92EE-69228A79CC90"
total 0
drwxr-xr-x  2 e.blindauer  staff  64 16 fév 12:11 .
drwxr-xr-x  3 e.blindauer  staff  96 16 fév 12:11 ..

feiniks · March 6, 2023, 4:05am

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/*?

Larrikin · March 12, 2023, 10:52pm

Hi @Jonathan. I followed all the steps exactly.

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

Running MacOS 13.2.1

feiniks · March 13, 2023, 7:40am

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.

Larrikin · March 13, 2023, 7:57am

I tried that and it didn’t work. Same issue. No libraries would show up and same error logs.

feiniks · March 14, 2023, 2:45am

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.