SeaDrive 2.0.10 released! Windows context menu extension and M1 CPU support for Mac

Merry Christmas and happy new year!

We have huge updates by the end of 2020. Hope you enjoy them.

  • [Win] Add context menu
  • [Mac] Support Apple Silicon M1 CPU
  • [Linux] Unmount on exit

Nice!! This is a very nice present! Thanks a lot!

I tested the context menu integration. Great!

@Jonathan Now, that the one most sought-after feature has been added back to SeaDrive, could you expand a bit on the future development of SeaDrive’s context menu and the drive client in general?

  • Will you add more functions to the context menu? (Create upload link, add password protection and auto expiration to link, …)
  • What are the development priorities for the client?
1 Like
  • install not working due to kernel driver not loading /should not ver 2.09 and 2.10 repair it ???/
  • there are no UNINSTALL instructions for macOS version, no uninstall package or script

Mac OS Big Sur 11.1 on M1 Silicon MacBook Pro

Hi @Peter_Vetrak

This is due to new security measure in the M1 MacBook: You have to change the options.

You just need to remove the Application. There is usually no uninstallation script for Mac Apps.

These are on the dev plan. Given that most functionalities are done for SeaDrive and sync client, our priority for clients is on incremental improvements and bug fixes. Also a native App for Apple CPU is planned. But it requires many third-party library support, such as Qt. So it’s scheduled for the long term. For now the client runs by the compatibility layer provided by macOS.

Tx for hint, I figured it by myself /using google/ but its really not easy for average user and I will advise my friends not to do it - its security risk. Native ARM Apple Silicon app is a must for the future.

Anyway, thank you for all effort - Seadrive is one of a few cloud apps with working “sync on demand like” on MacOS - on Synology and Qnap apps SyncOnDemand works only on Windows client.

Thank you very much @Jonathan

Hi Jonathan,
I take the liberty to note down the incremental improvements that I have noticed over the last releases:

1.) More options in context menu (i.e., manual file lock, create upload link for folder, create sharing link with password and auto-expiration)

2.) Unique names for SeaDrive nodes in the Explorer nav bar when more than one Seafile account is configured (to tell the accounts apart - see screenshot below)

3.) Improved user feedback (aka error message)
a.) when files are copied in one of the category folders and
b.) when files get copied in a read-only folder

4.) Option to disable one or several category folders (i.e., “Shared with all”, “My libraries”)

5.) Width-adjustable columns and an extra time column in the Transfer Progress dialog

6.) Width-adjustable columns in the Encrypted Libraries dialog (to tell the libraries apart with certain resolutions - see screenshot below)

7.) Thumbnail preview for libraries that are not “Always keep on this device”-d

Beyond incremental improvements, an interesting new feature for enterprises would be SSO with an Azure Token.


I did some more testing and I found one bug (one that most likely existed in previous versions too) and I made some observations that I’d like to report:

When I “Always keep on this device” a folder/library, I expect that any new file added to this folder/library gets downloaded automatically.

This is not the case. A new file, uploaded either via the web interface or by another user to the synced folder/library, is show in SeaDrive with a “syncing” status, but the file is never downloaded (see situation in the screenshot below). The transfer progress does not show any download activity and the status icon never changes to “synced”.

The file only get downloaded when I double-click on it.

When dropping a large file (think 5GB) in SeaDrive, the client starts the upload and the following behavior can be observed:
a.) There is no way of aborting the upload. When I delete the file, the upload continues. When I move the file, to another folder, the upload continues. When I shutdown SeaDrive and delete the file, the upload continues and the status icon changes to “cloud”. (I wonder how this is possible, where does SeaDrive take the file from?)
b.) The upload of files occurs strictly sequentially. Smaller files are not prioritized. The upload of the one large file may keep many smaller files from being synced to the server.
c.) The upload of the large file seems to block other features such as file locking.

1 Like

I’m running Seafile Drive Client 2.0.10 under Apple Silicon M1 (Mac mini). It works, but I’m wondering whether there is “native support”? In Activity Monitor it still shows “Intel”, so its running under Rosetta2?
Is this right?

Your observation is right.

As for your question:

1 Like

But: Am I so wrong to find that somewhat misleading?

Main thing: it works! Speed is not really an issue here.

For now it’s running in compatibility mode. We’ll work on native support later, when 3rd party libraries support M1.

This is the designed behavior. This is the same for sync client. The file is first copied into an internal cache area, indexed into chunks. Then the chunks are uploaded. So there is no way to stop syncing the file after it’s added to cache.

Good to know. Thanks. Just one follow up: You mention an internal cache area. Where is that?