Release v3.25.0-beta.4 (#2025)

Improvements for all users:

• Clients can now be disconnected from the remote Cozy even if it is no longer
  reachable (e.g. completely deleted or deleted after being moved to another
  domain). The local configuration and database will be wiped out.
• Changes that we failed to synchronize and should be retried will now be
  retried without previously running a check that validates if the
  synchronization should be successful. All changes made either on the local
  filesystem or the remote Cozy will thus be taken into account when retrying.
• We'll now verify if the Cozy has enough space before uploading files to avoid
  wasting time and resources to get an error at the end of the upload.
• Sometimes, the creation and modification dates of documents created on the
  remote Cozy at the initiative of the desktop client are different from those
  supplied by the client. This can come from the presence of EXIF metadata in
  photos for example. To avoid any refusal by the Cozy to apply future actions
  on these documents, we will now always pass the most recent modification date
  between that of the file system and that of the Cozy in requests sent to the
  Cozy.

See also known issues.

Happy syncing!

Release v3.25.0-beta.3 (#2019)

Improvements for all users:

• To make sure you're not tempted to give up on some changes because of a
  temporary error and end up with an desynchronized state and potentially lose
  data, we've removed the possibility to manually give up for most errors that
  are displayed to you in the main window. Instead, only conflicts with the
  remote Cozy will be droppable as we sometimes find ourselves in a situation
  where the conflict will never be resolved.

Improvements for Windows users:

• We've removed a duplicate retry mechanism for failed movements of locked
  documents (e.g. opened Office documents or being checked by an Anti-Virus
  software). This should speed up retries when the document is still locked.

See also known issues.

Happy syncing!

Release v3.25.0-beta.2 (#2014)

Improvements for all users:

• We upgraded the framework upon which our application is built, Electron, to
  v11.1.1 which is the latest stable version. This should bring more stability
  to the application overall and fix an issue on macOS Big Sur which was
  preventing the application from restarting after an upgrade.
• We've changed the way we handle the simultaneous deletions of the same
  document on the remote Cozy and the local filesystem so that any resulting
  synchronization conflict is only temporary (i.e. you would see an error
  message but it should be resolved during the following retry).
• Several improvements were made to synchronization error detection and messages
  over the previous beta release. Messages should be cleaner with an outstanding
  document name and filesystem locks detection should be better.

See also known issues.

Happy syncing!

Release v3.25.0-beta.1 (#2001)

Improvements for all users:

• Some synchronization errors will now be notified to you within the main window
  with information about the error itself and how to fix it and two options:
  giving up on the change if it can't be synchronized or requesting an early
  retry (automatic retries will be performed in the background).
  Know that the synchronization will be blocked by the failing change until an
  outcome is decided. This should avoid a lot of automatically dropped changes
  as we would otherwise stop retrying after the third attempt.

See also known issues.

Happy syncing!

A tree was promised

Improvements for all users:

• We fixed the way we fetch the local documents tree to both prevent failures
  when sending messages to support from the application and send the appropriate
  paths.

See also known issues.

Happy syncing!

Release v3.24.1-beta.1 (#1998)

Improvements for all users:

• We fixed the way we fetch the local documents tree to both prevent failures
  when sending messages to support from the application and send the appropriate
  paths.

See also known issues.

Happy syncing!

A new path to your pouch

Improvements for all users:

• This release lays the ground work for a future synchronization algorithm. We
  now store the complete remote metadata of each document and the local metadata
  of both files and directories. This will allow us to make deeper comparisons
  and take better action in complex situations (e.g. a file modification and
  renaming on the local filesystem with a parent directory renaming on the
  Cozy).
  Another part of this base work is the move to generated PouchDB records ids.
  Those were previously based on the document's path and this scheme had several
  limitations (e.g. when a document was moved or renamed, its record id had to
  change).
• The move to generated PouchDB ids allows you to synchronize documents whose
  name start with an underscore (_), in the root synchronization folder. Those
  previously resulted in reserved PouchDB ids and could not be stored thus
  synchronized.
• The upload requests rejection protection does not create memory leaks anymore
  as it will be cleaned up after the requests terminate, whether they're
  successful or not.
• When a new directory is linked with an existing directory on the other side
  (i.e. either the local filesystem or the remote Cozy) with the same name in
  the same parent directory, we'll update the existing directory's metadata with
  the new directory's metadata to make sure they're in sync.
• Now that we track the local metadata of files, we can still detect during the
  start-up local scan if a the file was updated on the local filesystem even if
  a remote update was saved in PouchDB but not synced before the client was
  stopped. With this detection we can decide if a conflict needs to be created
  or not without losing any data and stop applying the remote update in all
  cases.
• We'll now track more closely the local modifications resulting from the
  application on the filesystem of changes fetched from the remote Cozy. This is
  important especially for tracking movements and make sure opposite movements
  won't be wrongly "detected" after a client restart.

Improvements for Windows and Linux users:

• We've made sure the logic dedicated to the initial scan, run after a client
  start, won't be used after the initial scan is done. This was the source of
  bugs when applying folder movements fetched from the remote Cozy.

Improvements for Windows users:

• Files marked as executable and downloaded from the Cozy will remain marked as
  executable on the Cozy and all the devices recognizing this flag (i.e. on
  Linux or macOS). Since this flag is not recognized on Windows, synchronizing
  an executable file with a Windows device would previously remove the flag for
  everybody.

Improvements for macOS users:

• We're now handling moving the same document multiple times in a short delay
  and moving a document just downloaded from the Cozy to a path including UTF-8
  characters on HFS+ filesystems.

See also known issues.

Happy syncing!

Release v3.24.0-beta.3 (#1995)

Improvements for macOS users:

• We're now handling moving the same document multiple times in a short delay
  and moving a document just downloaded from the Cozy to a path including UTF-8
  characters on HFS+ filesystems.

See also known issues.

Happy syncing!

Release v3.24.0-beta.2 (#1991)

Improvements for all users:

• We'll now track more closely the local modifications resulting from the
  application on the filesystem of changes fetched from the remote Cozy. This is
  important especially for tracking movements and make sure opposite movements
  won't be wrongly "detected" after a client restart.

Improvements for windows and Linux users:

• We've made sure the logic dedicated to the initial scan, run after a client
  start, won't be used after the initial scan is done. This was the source of
  bugs when applying folder movements fetched from the remote Cozy.

See also known issues.

Happy syncing!

Release v3.24.0-beta.1 (#1988)

Improvements for all users:

• This release lays the ground work for a future synchronization algorithm. We
  now store the complete remote metadata of each document and the local metadata
  of both files and directories. This will allow us to make deeper comparisons
  and take better action in complex situations (e.g. a file modification and
  renaming on the local filesystem with a parent directory renaming on the
  Cozy).
  Another part of this base work is the move to generated PouchDB records ids.
  Those were previously based on the document's path and this scheme had several
  limitations (e.g. when a document was moved or renamed, its record id had to
  change).
• The move to generated PouchDB ids allows you to synchronize documents whose
  name start with an underscore (_), in the root synchronization folder. Those
  previously resulted in reserved PouchDB ids and could not be stored thus
  synchronized.
• The upload requests rejection protection does not create memory leaks anymore
  as it will be cleaned up after the requests terminate, whether they're
  successful or not.
• When a new directory is linked with an existing directory on the other side
  (i.e. either the local filesystem or the remote Cozy) with the same name in
  the same parent directory, we'll update the existing directory's metadata with
  the new directory's metadata to make sure they're in sync.
• Now that we track the local metadata of files, we can still detect during the
  start-up local scan if a the file was updated on the local filesystem even if
  a remote update was saved in PouchDB but not synced before the client was
  stopped. With this detection we can decide if a conflict needs to be created
  or not without losing any data and stop applying the remote update in all
  cases.

Improvements for Windows users:

• Files marked as executable and downloaded from the Cozy will remain marked as
  executable on the Cozy and all the devices recognizing this flag (i.e. on
  Linux or macOS). Since this flag is not recognized on Windows, synchronizing
  an executable file with a Windows device would previously remove the flag for
  everybody.

See also known issues.

Happy syncing!