SeaDrive for macOS 3.0.0 beta available for test

Announcement
#1

Hi Seafile Mac users,

SeaDrive for macOS 3.0.0 is now in beta! You’re welcome to download and test it!

You can download it here: https://download.seafile.com/f/c7ea2e5f00e14ac1b3b5/?dl=1

This major version update includes two anchor features:

  1. Virtual drive is implemented with File Provider API. No kernel extensions are installed any more.
  2. You can now access files in more than one accounts at the same time. Previously you have to switch among the accounts, which is not very convenient.

As kernel extensions are not the recommended way to write software on macOS in the future, switching to a native API will make SeaDrive more future-proved. This also makes installing SeaDrive on M1 Macs much easier.

Features not supported yet:

  1. File locking
  2. Folder permissions
  3. Image thumbnails

Please note that automatic file locking for Office files doesn’t work with File Provider API. The API deliberately hide the Office temp files. So there is no way to detect opening of Office files.

3 Likes
Seadrive doesn't work on MacOS Ventura Beta
SeaDrive for macOS 3.0.1 Beta is available for testing
#2

Running this package on a M1 Max on Ventura does not work; looks like it sends 2 requests on start up, but never completes the files list download. I also cannot edit any of the aoo settings - everything is grayed out. I have also fully de-installed the client, rebooted and then reinstall the client.

Here are errors from the 'local logfile of my seadrive client:

[11/22/22 18:50:30] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:32] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:34] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:36] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:38] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:40] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:42] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:44] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:46] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:48] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:50] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:52] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:54] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:56] pipe client failed to connect to server: No such file or directory
[11/22/22 18:50:58] pipe client failed to connect to server: No such file or directory
[11/22/22 18:51:00] pipe client failed to connect to server: No such file or directory
[11/22/22 18:51:02] pipe client failed to connect to server: No such file or directory
[11/22/22 18:51:04] pipe client failed to connect to server: No such file or directory

#3

but never completes the files list download. I also cannot edit any of the aoo settings …

These are expected behaviors on the GUI when the File Provider plugin fails to start or be connected. Log messages also show evidence that the GUI has lost connection.

To find out the cause, please check whether there is a newly created item (named SeaDrive) in the sidebar of Finder. (Assuming that you have already logged into an account.)

  • If it does not exist, then check File Provider API logs, which should present earlier than connection failure messages.
  • If it does exist, then click on the sidebar item and check for error messages on the top banner. Any crash reports for SeaDrive from the Console.app are also helpful.
#4

Looks strange… nothing inside the folders ( MacOS BigSur 11.7.1 )

Bildschirmfoto 2022-11-26 um 09.18.28
Bildschirmfoto 2022-11-26 um 09.18.28640×1032 168 KB

#5

I got errors like this:

[11/28/22 19:20:28] failed to send rpc call: Broken pipe
[11/28/22 19:20:28] failed to get sync errors: Transport Error

[11/28/22 19:20:29] failed to send rpc call: Broken pipe
[11/28/22 19:20:29] failed to get seadrive.events: Transport Error

[11/28/22 19:20:29] failed to send rpc call: Broken pipe
[11/28/22 19:20:29] failed to get sync notification: Transport Error

[11/28/22 19:20:29] failed to send rpc call: Broken pipe
[11/28/22 19:20:29] failed to get global sync status: Transport Error

macOS: 13.0.1

And all setting options are not configurable. For example, I unchecked the “Notify when libraries are synchronized” and click “OK”. When I get back to settings, my change had not been saved. Looks like now it won’t record user changes in settings.

#6

Have you tried the steps here? Can you share the complete seadrive-gui.log and also seadrive.log? Please send them to support@seafile.com.

#7

@Blackbelt-Ninja It’s a known bug that so many category folders are created. But have you checked whether there are files under the category folders without a number? That should be the first category folder that was created and the files should be in them.

#8

It keeps going creating more and more folders… Files are inside the folder without numbers ( inside also keeps creating new folders with numbers increasing ). Finally all Folders without numbers disappear…

Looks more like an alpha than beta, unfortunately.

#9

similiar behaviour here. Completely uninstalled 2.0.24, rebooted, installed 3.0.0 beta1 and logged in “successfully” with 2FA. Stuck on retrieving files list.

EDIT: MacBook Pro 16" M1Max, macOS Ventura 13.0.1

[12/02/22 12:07:06] pipe client failed to connect to server: No such file or directory
[12/02/22 12:07:06] [File Provider] Listing domains
[12/02/22 12:07:06] [File Provider] Adding domain “1edd2and945bd2dd2fbf8e16cbaa56d0” “Name Surname(cloudname (added space to prevent it from being a link in post) .address.com)”
[12/02/22 12:07:08] pipe client failed to connect to server: No such file or directory

eventually switching to

[12/02/22 12:17:52] pipe client failed to connect to server: Bad file descriptor
[12/02/22 12:17:54] pipe client failed to connect to server: Bad file descriptor
[12/02/22 12:17:56] pipe client failed to connect to server: Bad file descriptor

#10

@PivotMasterNM Have you tried these steps?

Please note that you have to enable the extension in the Finder window. Otherwise the SeaDrive extension will not be loaded so it won’t work.

#11

I’ve tried them. after a few reboots it suddenly started working. Unfortunately cannot tell you whether the steps, the reboots or a higher mysterious power made this suddenly work.

An extra question: we use the spacebar “preview” option a lot on our seadrive. With this version, I have to manually click the cloud+arrow icon first to download the file, previewing before that doesn’t work and doesn’t initiate the download. Will that be “fixed” in the future?

#12

Does this work with encrypted libraries? I can’t find any place to put in my encryption password on my libraries, so whilst it shows my libraries existing in the Finder, when I try and access my library the log file states its encrypted (and the finder simply fails to do anything further).

#13

Is there some kind of trick to installing? I uninstalled the 2.x client and installed the package attached and it installs fine, but I can’t find it in Applications or anywhere I can find.

#14

Yes it does. In the tray icon menu, you can choose to show encrypted libraries. When you choose to sync an encrypted library from the list, you’ll be prompt for password.

#15

Strange. Have you tried installing again? Restarting the computer?

#16

Yeah, I downloaded and installed SeaDrive-3.0.0-beta1.pkg, rebooted and it’s not in Applications and nothing happens to start automatically.

#17

So I made a little progress today. rebooted, redownloaded and installed the beta and this time it worked.

But now I am getting the same issue as the people above with the
[01/07/23 13:34:43] pipe client failed to connect to server: No such file or directory

I’ve tried to reboot a bunch, removed/re-added the account, tried turning off 2FA on the server, but nothing seems to be working. I am confused by what @Jonathan said of enabling the extension in Finder. Where do I do that? It seems to be not connecting the the server, but I’ve had no issues on the other non-beta clients I have.

#18

Ok, I figured out why my issue was happening. My Seafile server is fronted by Caddy, and Seadrive seems to be angry about that. I pointed Seadrive to the local IP and port of the Seafile server, and that worked. And I see the Finder extension button to enable.

Does anyone have any suggestions for what needs to be configured on the Caddy side? I am going to look at Caddy’s forums to make sure I’ve configured what they recommend.

1 Like
#19

I’m getting another issue related to APFS storage.

The error is [01/11/23 06:49:26] [File Provider] Error adding domain: Error Domain=NSCocoaErrorDomain Code=3328 "SeaDrive requires APFS, but the file system for the home volume is “Mac OS étendu (sensible à la casse, journalisé)”." UserInfo={NSLocalizedDescription=SeaDrive requires APFS, but the file system for the home volume is “Mac OS étendu (sensible à la casse, journalisé)”., NSLocalizedRecoverySuggestion=Convert the home volume to APFS in Disk Utility.}

The disk is allready a APFS, some check seems to use a i18n label instead the real FS type.

   File System Personality:   Case-sensitive APFS
   Type (Bundle):             apfs
   Name (User Visible):       APFS (Case-sensitive)

The check must be on type instead of Name

#20

I went back to this after Jonathon’s follow ups and I can confirm it’s working now on my M1 Max. I’m not seeing any glaring or obvious errors at this stage. All I did was install the 3 beta package right over the top of the existing 2 (although I had done that first install noted above). For me, it was going into finder, in near the top on the left is a clickable ‘button’ to enable the connection/service. So I think if you make that more clear - too bad I don’t have screenshot. That would likely clear that confusion up if there is any on that end.