Skip to content

Releases: cozy-labs/cozy-desktop

Release v3.23.0-beta.5 (#1954)

09 Sep 13:08
28d260e
Compare
Choose a tag to compare
Pre-release

Improvements for macOS users:

  • The order in which changes fetched from the remote Cozy were processed could
    hinder the paths normalization and lead to issues like conflicts.
    We're now sorting changes before the normalization to make sure the process
    will complete as expected.

See also known issues.

Happy syncing!

Release v3.23.0-beta.4 (#1952)

07 Sep 14:49
e24dcd3
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • Fixes the infinite spinner of the Updater window, displayed when download
    progress info is not available.

See also known issues.

Happy syncing!

Release v3.23.0-beta.3 (#1950)

07 Sep 12:22
ad36263
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • Fixes the displayed icon of recently synchronized files whose type is
    identified as text.

See also known issues.

Happy syncing!

Release v3.23.0-beta.2 (#1948)

28 Aug 17:52
ece1d80
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • Fixes a technical issue that prevented the built application from running.

See also known issues.

Happy syncing!

Release v3.23.0-beta.1 (#1946)

28 Aug 15:31
f1dc946
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • We upgraded the framework upon which our application is built, Electron, to
    v9.2.1 which is the 2nd latest major version (v10.0.0 was released 4 days
    ago). This should bring more stability to the application overall and prevent
    some crashes. We can also expect smaller bundles. This upgrade brings us
    official support back for a while.
  • Data migrations run after some client upgrades should not prevent not fully
    synchronized changes from being detected and synchronized after the
    migration.
  • Documents added on your remote Cozy, detected by the client but not fully
    synchronized before it is stopped should be synchronized correctly after the
    next client launch. The client should not try to delete them on your Cozy
    because it does not find them locally (the deletions never went through
    fortunately).

Improvements for Windows users:

  • With the Electron upgrade, you should be able to disconnect your client from
    your remote Cozy via the client interface.

Improvements for Linux users:

  • If you have disabled the client autolaunch upon your computer startup it
    should not be re-enabled during your next application launch anymore.

See also known issues.

Happy syncing!

Experience the normal

13 Aug 13:43
9529011
Compare
Choose a tag to compare

Improvements for all users:

  • As a multi-device platform, Cozy Cloud tries to keep the modification dates of
    documents in sync across all your devices (i.e. Drive Web, Drive Mobile,
    Cozy Desktop, other people's Cozies…). When modifications happen on the Cozy
    itself, the modification date is set by the server. On the other hand, when
    the modification is made on on your computer, we get the date from your
    filesystem. We were using the most recent date between the content
    modification date and the metadata modification date but we think the content
    modification date is the most important and that it should not be affected by
    movements, renamings, permission changes, etc.
    For this reason, from now on we will only use the content modification date on
    Cozy Desktop.
  • Files with remote creation or modification dates in a timezone other than UTC
    would raise an error in the remote watcher when converting them into PouchDB
    records.
    We're now rounding those dates with a timezone agnostic method and those
    errors should not happen anymore.
  • When you start your Cozy Desktop client, we scan the whole synchronization
    folder on your computer to detect document additions, modifications,
    movements… The file modification detection is done in 2 steps to avoid time
    consuming computation:
    1. we compare the modification date fetched from your filesystem with the one
      we last saved in our database
    2. if and only if they differ, we compute the file's checksum to compare it
      with the one saved in the database
      Our modification date was not completely reliable, especially on Windows and
      Linux so we were computing a lot of checksums for files that were not modified
      while the client was stopped.
      We're now using the local file state which holds a reliable content
      modification date and we should avoid a lot of checksum computations thus
      saving you a lot of time during a client start and a lot of CPU resources.
  • The list of recently synchronized files and the linked Cozy information would
    sometimes not be displayed after a client restart, especially on Windows.
    The data was correctly persisted though and we've made sure it is correctly
    loaded and displayed now.
  • The list of recently synchronized files could be persisted multiple times
    concurrently, leading to malformed JSON content which could not be loaded back
    into the client's GUI during the next start.
    We're now making sure each write is done sequentially so that the list is
    always saved as valid JSON.
  • The list of recently synchronized files could contain folder items when their
    parent was moved or renamed.
    We're now making sure only file items will be displayed in this list until we
    officially support folder items.
  • We increased the number of file types that will be displayed with a specific
    icon to help you check more easily which elements were synchronized. This
    includes 2 new icons for links (i.e. .url files) and contacts (i.e. .vcf
    files).
  • The autolaunch setting could be displayed as enabled when it was disabled from
    the OS settings panel instead of the Cozy Desktop client settings.
    We've made sure the interface shows the actual value of this setting and the
    switch is off when the autolaunch is disabled.

Improvements for Windows and macOS users:

  • A file name case change on the remote Cozy followed by a remote content update
    could lead in some situations to the local file being trashed on the computer.
    On macOS this could also happen if the renaming was simply a normalization
    change or there was a normalization difference in the name of one of its
    ancestors.
    We've changed the way we handle the conjunction of those 2 changes to make
    sure case and normalization changes don't affect them. The file should now be
    properly moved and updated on the local filesystem.

Improvements for Windows users:

  • Some Windows software save modifications made on a file by moving this file to
    a backup location before writing the new version in its stead. The events
    received by Cozy Desktop in this situation were not correctly interpreted as
    we did not expect it and the client would trash the file on the remote Cozy
    before uploading the new version. If the client were to be stopped before the
    new version was uploaded, the file could stay trashed until the client was
    started again.
    We're now expecting this suite of events to happen and are applying a specific
    behavior to transform them into a file update that will be correctly
    propagated to the remote Cozy as one change thus avoiding situations where the
    file is trashed.
  • The local file state introduced in the previous release was not fully
    populated on Windows when propagating the addition of a file from the Cozy to
    the local filesystem due to a bug.
    While it should have been without consequences, the bug was fixed and the
    features requiring this local state to be populated (e.g. limiting the number
    of file checksum computations during a client start) should be fully
    functional.

Improvements for macOS users:

  • A lot of improvements around the support of NFD/NFC UTF-8 normalizations for
    document paths, especially when they differ between the remote Cozy and the
    local filesystem.
    You shouldn't see synchronization errors due to the renaming, movement,
    addition, modification of files and folders with accented names.

See also known issues.

Happy syncing!

Release v3.22.0-beta.6 (#1935)

12 Aug 14:29
984007e
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • The autolaunch setting could be displayed as enabled when it was disabled from
    the OS settings panel instead of the Cozy Desktop client settings.
    We've made sure the interface shows the actual value of this setting and the
    switch is off when the autolaunch is disabled.

See also known issues.

Happy syncing!

Release v3.22.0-beta.5 (#1933)

08 Aug 16:10
f06398e
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • The list of recently synchronized files could contain folder items when their
    parent was moved or renamed.
    We're now making sure only file items will be displayed in this list until we
    officially support folder items.
  • We increased the number of file types that will be displayed with a specific
    icon to help you check more easily which elements were synchronized. This
    includes 2 new icons for links (i.e. .url files) and contacts (i.e. .vcf
    files).

See also known issues.

Happy syncing!

Release v3.22.0-beta.4 (#1930)

08 Aug 14:08
f213c28
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • The list of recently synchronized files could be persisted multiple times
    concurrently, leading to malformed JSON content which could not be loaded back
    into the client's GUI during the next start.
    We're now making sure each write is done sequentially so that the list is
    always saved as valid JSON.

See also known issues.

Happy syncing!

Release v3.22.0-beta.3 (#1928)

31 Jul 10:30
7a33ed8
Compare
Choose a tag to compare
Pre-release

Improvements for all users:

  • The list of recently synchronized files and the linked Cozy information would
    sometimes not be displayed after a client restart, especially on Windows.
    The data was correctly persisted though and we've made sure it is correctly
    loaded and displayed now.

See also known issues.

Happy syncing!