No update notification in the desktop/sync clients — a real gap for production use

Seafile Client
1

I’d like to raise something we ran into recently, both as a concrete incident and as a more general concern about the clients.

What happened: We were running the macOS sync client 9.0.11 against our Seafile Professional server. We hit a serious problem where renaming shared folders led to file-structure corruption — and notably, this happened even when the rename was performed server-side through the web interface rather than locally. After a fairly long troubleshooting session, we traced the root cause to the client version: 9.0.13 (2025/04/02) lists a fix for a macOS bug in handling rename events that can cause files to be moved to the wrong folder. Once we updated the client, the issue disappeared. [Relevant Client Changelog]

We’re not posting to complain about a single bug — bugs happen, and this one was fixed promptly. What concerns us is how we ended up stuck on an affected version for so long. The desktop and sync clients have no auto-update mechanism, and as far as we can tell, no notification when a newer version exists either. There’s nothing in the running client that tells an admin or an end user “you’re behind, and the version you’re on has a known data-integrity fix waiting for you.”

For a product positioned as enterprise-grade file infrastructure, we think that’s a real gap. In our case it directly translated a fixed, known bug into hours of diagnosis and a genuine risk to data integrity, simply because nothing surfaced the fact that an update was available. The web UI and server side were never the problem — the silent staleness on the client was.

A few things that would meaningfully reduce this risk, roughly in order of how useful we’d find them:

  • An in-client notification when a newer stable version is available (even a passive banner would help).

  • An optional auto-update path for the desktop/sync/drive clients, or at minimum a documented mechanism admins can push through.

  • Surfacing known data-integrity fixes more prominently in release notes, so it’s obvious which updates are “should update now” rather than “nice to have.”

For what it’s worth, our research shows that earlier client versions did include new-version-check functionality (an automatic check on startup in 2.x, an auto-update check added in 6.0.6, and a ‘Check new version’ button in the About dialog). Whatever the current state, we’d value having a clear update-notification path in the clients again.

Has anyone else hit version-staleness causing avoidable issues, and are there workarounds others use today to keep clients current across a fleet? Curious whether we’re missing an existing option here.

2 Likes
2

Hi there,

I feel you on that one, I never really witnessed the “issue” as I’m personally using Linux/Arch which package manger would update SeaDrive/SeaFile Client per OS standards.

Although having deployed SeaFile for small teams of mainly Windows users, I could see that indeed, the clients are staying right where you left them – no exactly great.

I wonder how this is handled in bigger shops – got a powershell script to do the update per schedules although that would require admin rights on the endpoint etc…

Hence yes, Seafile Client auto-update would be great yes.

Cheers,
m.

3

Hello,

I mean this in a respectul, non-negative way, but if this is important for your organization, perhaps you should investigate how you manage your environment. In our enterprise environment we do not rely on software updaters to tell us or to upgrade software. We have management software that either does this for us, or we setup alert systems. We have maintenance schedules to make sure updates are being installed.

For sites and software that do not have any way native way alert us (i.e no rss/mailing list, no version check), we do some quick scripting to either parse a version history page or download the latest installer and compare. If none of that is possible, we add it to a “manual” list of software and we manually check for a new version as part of normally scheduled maintenance.

I did some quick searching and it appears there are several enterprise-level management tools available for MacOS, though the ones I quickly looked at did not appear to natively handle/have a template for seafile clients - though they all have the ability to install/manage seafile, they just need a human to press the button/upload the installer to the management system.

If seafile decides to (re)add a version check, I humbly request it be able to be disabled so our end users here are not bothered by software updates alert (they can’t install the software themselves).

Have a nice day!

4

Not related to “organizations” or anything, it is really hard to recommend Seafile for any non-Pro user (e.g. family!!!) because of this missing update feature. And if the whole software industry provides update notifications and mechanisms, maybe Seafile is on the wrong side and not everybody else.

5

We’ll look into it. We had auto update before but the mechanism is not easy to maintain.

1 Like