Because we're only human

Improvements for all users:

• We fixed an issue where copies of conflicting files would not be created at
  the right path.

Improvements for Windows & GNU/Linux users:

• We improved our test harness regarding the initial scan of the local synced
  directory. Those new tests already allowed us to identify and fix an issue
  (see next point).
• When moving a directory then updating a descendant file while the app was
  stopped, the file change would not be synced. This now works as expected.
  This used to work but was broken at some point. The new tests should prevent
  this to happen again.
• Although some files and directories were correctly ignored during initial
  scan, this was not done immediately, resulting in more work for the app.
  They are now ignored as soon as possible. This should also prevent a couple
  of issues with some Windows system directories.

See also known issues.

Happy syncing!

Small talk

Improvements for Windows & macOS users:

• The application code signing certificate was updated.

Improvements for Windows & GNU/Linux users:

• When a file or directory is moved or renamed from an ignored path to a
  non-ignored one, it is now handled as a creation.
• When a file or directory is moved or renamed from a non-ignored path to an
  ignored one, it is now handled as a deletion.

See also known issues.

Happy syncing!

What is your sign?

Improvements for Windows & macOS users:

• The application code signing certificate was updated.

See also known issues.

Happy syncing!

Moves and ignorance are not ennemies

Improvements for Windows & GNU/Linux users:

• When a file or directory is moved or renamed from an ignored path to a
  non-ignored one, it is now handled as a creation.
• When a file or directory is moved or renamed from a non-ignored path to an
  ignored one, it is now handled as a deletion.

See also known issues.

Happy syncing!

It's all about the error message

Improvements for all users:

• We changed the status label when we catch an error that was not specific
  enough for us to offer you a simple resolution. In this situation we were
  stating that the synchronisation was impossible when in most cases, some
  changes can have been reconciliated and synchronised. We're now saying that
  the synchronisation was incomplete. You should still contact us in this
  situation as we might be able to offer you some help.
• We improved error handling in our auto-update component. Hopefully this
  should make it easier for people with flaky connections to get the latest
  version of the app.
• Whenever we can't reconciliate some changes coming from your remote Cozy with
  your local documents, we try to inform you via special status label and icon.
  Those issues can have different origins but most of them were notified to you
  as your computer lacking an internet connection. We've made some changes to
  display the No Internet connection status only when we experience network
  issues and a generic synchronisation issues status when we can't be more
  precise.
• To help you keep your app up-to-date, we have a mechanism that checks for new
  versions every 24 hours. While we do that check, the app does not attempt to
  synchronise anything to avoid stopping the process while the new version is
  installed. We set a maximum wait time of 5 seconds for the check so that you
  won't get stuck in that state for too long. Unfortunately, we've noticed that
  some users hit that timeout because the check was taking too long and don't
  get the new version notification, probably because of a slow Internet
  connection.
  We've decided to increase the maximum wait time to 10 seconds to make sure
  those users are informed that a new version is available. This should have no
  impact for users with a fast Internet connection.
• In some situations, we can try to reconciliate changes on documents whose
  ancestor we don't know (e.g. a change on directory/file when we've never
  received the creation of directory/). To help merge those changes we try to
  recreate the missing ancestor. However, we found out that recreating a valid
  ancestor for changes coming from your remote Cozy is plain impossible since we
  don't have its remote metadata such as its identifier. This was causing merge
  issues leading to increased merge times for subsequent changes on other
  documents, increased log files sizes and no way to fix the situation.
  We've made the decision to stop trying to recreate missing ancestors of remote
  changes and ignore those issues altogether. This means that the changes won't
  be merged (i.e. this is no different than the current situation) but we won't
  try to merge them over and over, each time we pull changes from the remote
  Cozy (i.e. every minute or so). We will still detect and attempt to merge
  changes on the documents although the situation will be similar until a change
  on the ancestor is made. But this also means we'll be able to merge all those
  changes if you make a change on the ancestor we didn't get the chance to save.

See also known issues.

Happy syncing!

Get Up, Stand Up!

Improvements for all users:

• We improved error handling in our auto-update component. Hopefully this
  should make it easier for people with flaky connections to get the latest
  version of the app.

See also known issues.

Happy syncing!

It might be off but not offline

Improvements for all users:

• Whenever we can't reconciliate some changes coming from your remote Cozy with
  your local documents, we try to inform you via special status label and icon.
  Those issues can have different origins but most of them were notified to you
  as your computer lacking an internet connection. We've made some changes to
  display the No Internet connection status only when we experience network
  issues and a generic synchronisation issues status when we can't be more
  precise.

See also known issues.

Happy syncing!

We're trying to help you. Really!

Improvements for all users:

• To help you keep your app up-to-date, we have a mechanism that checks for new
  versions every 24 hours. While we do that check, the app does not attempt to
  synchronise anything to avoid stopping the process while the new version is
  installed. We set a maximum wait time of 5 seconds for the check so that you
  won't get stuck in that state for too long. Unfortunately, we've noticed that
  some users hit that timeout because the check was taking too long and don't
  get the new version notification, probably because of a slow Internet
  connection.
  We've decided to increase the maximum wait time to 10 seconds to make sure
  those users are informed that a new version is available. This should have no
  impact for users with a fast Internet connection.
• In some situations, we can try to reconciliate changes on documents whose
  ancestor we don't know (e.g. a change on directory/file when we've never
  received the creation of directory/). To help merge those changes we try to
  recreate the missing ancestor. However, we found out that recreating a valid
  ancestor for changes coming from your remote Cozy is plain impossible since we
  don't have its remote metadata such as its identifier. This was causing merge
  issues leading to increased merge times for subsequent changes on other
  documents, increased log files sizes and no way to fix the situation.
  We've made the decision to stop trying to recreate missing ancestors of remote
  changes and ignore those issues altogether. This means that the changes won't
  be merged (i.e. this is no different than the current situation) but we won't
  try to merge them over and over, each time we pull changes from the remote
  Cozy (i.e. every minute or so). We will still detect and attempt to merge
  changes on the documents although the situation will be similar until a change
  on the ancestor is made. But this also means we'll be able to merge all those
  changes if you make a change on the ancestor we didn't get the chance to save.

See also known issues.

Happy syncing!

Temporary is temporary

Improvements for all users:

• We added a new icon set for the Offline status. Prior to this version,
  whenever we detected you might be disconnected from the Internet, we would
  display a "pause" icon with the "Disconnected" status label. We're now
  displaying a shadowed version of the main icon and a "No Internet connection"
  status label. We hope this is clearer to you.
• We fixed a bug in the way we sort changes coming from your remote Cozy. For
  some changes like the replacement of a file, the order in which we receive
  changes from the remote Cozy is crucial to applying it correctly on the local
  filesystem. In this particular case, we were not always sorting correctly the
  deletion and recreation of the file (or folder) which could lead to documents
  disappearing or conflicts to appear.
• We are now able to detect the use of a temporary file in some situations and
  correctly handle it (i.e. not move it to the trash and synchronise the new
  version).
• We've updated again some of our dependencies that don't require changes in
  our code. Those are the same that were upgraded in v3.13.1-alpha.1
  then downgraded back in v3.13.1-beta.1.
  We investigated, identified and excluded the problematic updates, so
  networking should work as expected this time.

Improvements for Windows & GNU/Linux users:

• When renaming folders and deleting part of their content while the client
  was stopped, the deletion should now be properly handled on restart.

Improvements for GNU/Linux users:

• We've mitigated an issue LibreOffice users could encounter while saving.
  LibreOffice uses an intermediary temporary file when saving and in some
  situations we could end up deleting the file altogether or move the previous
  version to the Cozy's trash and even not be able to synchronise the new
  version.
  We're now ignoring those temporary files (i.e. with extension .osl-tmp)
  which results in a correct update of the office document.

Improvements for contributors:

• We've decided to run prettier over our entire codebase with the cozy-app
  eslint config and to keep using it from now on. This will remove the need to
  check for syntax errors and improve homogeneity between Cozy Cloud javascript
  projects.

Changes that should have no effects:

• We did some minimal refactoring on our proxy setup to introduce some tests.
  There should be no effects on the way the proxy works.

There are some known issues that we'll tackle in the next releases:

• When we don't detect any update closely following the temporary file deletion
  and that file is not ignored, we end up deleting the file that was saved.
  This is a more general situation and should be fixed very soon.

See also known issues.

Happy syncing!

Dependencies Return!

Improvements for all users:

• We've updated again some of our dependencies that don't require changes in
  our code. Those are the same that were upgraded in v3.13.1-alpha.1
  then downgraded back in v3.13.1-beta.1.
  We investigated, identified and excluded the problematic updates, so
  networking should work as expected this time.

See also known issues.

Happy syncing!