Improvements for all users:
- In case your client enters an error state, the manual synchronisation button will now display is normal label instead of the error label which is already display in the window's top bar.
- We fixed an issue with conflicting document names in the previous version but introduced in the process a bug with files without extensions. If we detected a conflict on a file without extensions that already had the conflict suffix, we would use the milliseconds part of the previous conflict suffix as the new file extension. We're now correctly handling conflict suffixes replacement for all types of documents, with or without extensions.
- We recently tried to reduce the error kinds that would lead to a "No Internet connection" status to network errors only and introduced a new "Synchronization incomplete" status for cases where one or several of yours documents could not be synchronised but some could. However, we discovered the network errors we're getting from the remote Cozy don't have the shape we expected and were detected as synchronisation errors thus displaying the "Synchronization incomplete" status. All network errors are now correctly detected and handled as "No Internet connection" errors with a retry every second until the connection to your Cozy is back.
- We took this opportunity to handle PouchDB errors thrown when a file or
directory name starts with an
_(i.e. those are reserved PouchDB words) as a synchronisation error instead of a network error.
Improvements for MacOS users:
- We were forbidding the usage of the
:character in folder and file names as this is a forbidden character in the MacOS Finder application. However, the Cozy Desktop application is working at a lower level where:characters are allowed. Those are then displayed as/characters in Finder. Note that any/you see in one of your documents' name in Finder, will be synchronised as a:in your Cozy and vice versa.
See also known issues.
Happy syncing!
Improvements for all users:
- In case your client enters an error state, the manual synchronisation button will now display is normal label instead of the error label which is already display in the window's top bar.
- We fixed an issue with conflicting document names in the previous version but introduced in the process a bug with files without extensions. If we detected a conflict on a file without extensions that already had the conflict suffix, we would use the milliseconds part of the previous conflict suffix as the new file extension. We're now correctly handling conflict suffixes replacement for all types of documents, with or without extensions.
- We recently tried to reduce the error kinds that would lead to a "No Internet connection" status to network errors only and introduced a new "Synchronization incomplete" status for cases where one or several of yours documents could not be synchronised but some could. However, we discovered the network errors we're getting from the remote Cozy don't have the shape we expected and were detected as synchronisation errors thus displaying the "Synchronization incomplete" status. All network errors are now correctly detected and handled as "No Internet connection" errors with a retry every second until the connection to your Cozy is back.
- We took this opportunity to handle PouchDB errors thrown when a file or
directory name starts with an
_(i.e. those are reserved PouchDB words) as a synchronisation error instead of a network error.
Improvements for MacOS users:
- We were forbidding the usage of the
:character in folder and file names as this is a forbidden character in the MacOS Finder application. However, the Cozy Desktop application is working at a lower level where:characters are allowed. Those are then displayed as/characters in Finder. Note that any/you see in one of your documents' name in Finder, will be synchronised as a:in your Cozy and vice versa.
See also known issues.
Happy syncing!
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 a couple of issues (see next points).
- 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.
- We've found out that if a file is replaced and it's parent directory moved or renamed while the client was stopped, we were issuing a deleted event for the file at its new location because its inode is different and we didn't match it with its Pouch document. However, we have logic that prevents issuing deleted events for paths we have seen during the initial scan. The problem here is that we were correcting the file's path (i.e. we follow its parent move and use its new location in the file's path) after checking if we had seen the path during the initial scan. We're now correcting the path before doing the check so a scan event of the new file's path will prevent the initialDiff from issuing a deleted event for it.
- 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!
Improvements for Windows & GNU/Linux users:
- We've found out that if a file is replaced and it's parent directory moved or renamed while the client was stopped, we were issuing a deleted event for the file at its new location because its inode is different and we didn't match it with its Pouch document. However, we have logic that prevents issuing deleted events for paths we have seen during the initial scan. The problem here is that we were correcting the file's path (i.e. we follow its parent move and use its new location in the file's path) after checking if we had seen the path during the initial scan. We're now correcting the path before doing the check so a scan event of the new file's path will prevent the initialDiff from issuing a deleted event for it.
See also known issues.
Happy syncing!
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!
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!
Improvements for Windows & macOS users:
- The application code signing certificate was updated.
See also known issues.
Happy syncing!
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!
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/filewhen we've never received the creation ofdirectory/). 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!
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!
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!
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/filewhen we've never received the creation ofdirectory/). 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!
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!
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!
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 all users:
- The solution above applies only to LibreOffice users on Linux while there are other software saving through a temporary file. 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).
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!
Improvements for MacOS users:
- We recently introduced a new icon for the Disconnected app status when we can't reach your remote Cozy. On MacOS, this icon was rendered incorrectly within the app itself, in the status bar. We changed the icon to be of the expected color in the systray and the app status bar.
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.
See also known issues.
Happy syncing!
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.
See also known issues.
Happy syncing!
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 all users:
- We downgraded the dependencies upgraded in v3.13.1-alpha.1 because the upgrade broke networking. It should work again now.
See also known issues.
Happy syncing!
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.
Improvements for all users:
- We've updated some of our dependencies. There shouldn't be any consequence but it's just good hygiene and could potentially fix issues we don't even know.
See also known issues.
Happy syncing!
Improvements for Windows and GNU/Linux users:
- We completely revamped the local watcher (the component looking for changes in your local Cozy Drive directory). It should now be faster and more reliable when synchronizing live changes. Expect a few more optimizations regarding the initial scan very soon.
- The watcher type used (i.e. atom or chokidar) can still be chosen via the config file. The new watcher (atom) is the default on Windows and GNU/Linux.
Improvements for all users:
- We've updated our icons to reflect the new Cozy branding with a deep blue instead of the faded one and more of that blue around our lovely little cloud.
- The remote watcher now ignores changes with a revision lower than the one we've saved on the associated document in the local Pouch. Failing to do so was leading to files disappearing locally (before reappearing a short while later) during their upload to the Cozy. This could also be the cause of unexpected and undocumented behavior.
- Since it could be surprising and even misleading, we've removed the count of the remaining items to be synchronised until we can be sure it's always accurate. In the meantime, you'll see a simpler message indicating the client is syncing.
- We fixed an issue we had in the generation of a conflict file name where the conflict suffixes could be added indefinitely in case the conflicting file would get in conflict again. It happened that directories or files without an extension were still subject to a similar issue. We made sure they will only ever have one conflict suffix added to their name even in case they get in conflict again.
- During the synchronisation process, a document can change either locally (e.g. its checksum has changed because of a modification) or on the Cozy (e.g. the file was moved or modified by another client). In this situation the Cozy won't accept the change and will answer with an error. When we receive errors from the Cozy we retry up to 3 times to apply the change but if the document has changed, we will never be able to apply it and will only lose time by retrying. We now retry only on network and disk space errors to speed up the synchronisation of files rapidly changing.
- Files and folders named like a volume (e.g. C:) and at the root of the folder watched by Cozy Desktop could lead to an infinite loop if they or any of their children were ever modified. Those are now handled properly and won't be ignored either.
- Fixed a race condition case were a sharing could be disabled when a folder was moved locally while another one was added remotely to the same destination.
- We updated one of our main dependencies, Electron, to its 2.x version. We are still not using the latest version but this one brings us back support from the Electron team and security fixes. Other updates will come in the following releases.
See also known issues.
Happy syncing!
Improvements for Windows and GNU/Linux users:
- We fixed the last known issue regarding files and directories renamed while the client is stopped using the new watcher. The next release should be a stable one! 🚀
See also known issues.
Happy syncing!
Improvements for all users:
- The remote watcher now ignores changes with a revision lower than the one we've saved on the associated document in the local Pouch. Failing to do so was leading to files disappearing locally (before reappearing a short while later) during their upload to the Cozy. This could also be the cause of unexpected and undocumented behavior.
Improvements for MacOS users:
- When updating the Cozy branding, we messed up the alignment of icons in the MacOS installer. The Cozy app icon, the arrow and the Applications folder are now properly aligned and vertically centered in the installer window.
See also known issues.
Happy syncing!
Improvements for all users:
- We've updated our icons to reflect the new Cozy branding with a deep blue instead of the faded one and more of that blue around our lovely little cloud.
Improvements for Windows and GNU/Linux users:
- With our new watcher, some remote movements that were detected, taken into account but not applied locally (i.e. the file or directory itself would not have been moved on the filesystem) because the client was stopped in the middle of the synchronisation process would not be correctly applied after the client is relaunched. In this situation, we would end up duplicating the document that was moved, at its previous path. We made sure we detect unapplied remote movements so we can finish applying them and not duplicate your documents.
- Since it could be surprising and even misleading, we've removed the count of the remaining items to be synchronised until we can be sure it's always accurate. In the meantime, you'll see a simpler message indicating the client is syncing.
See also known issues.
Happy syncing!
Improvements for Windows and GNU/Linux users:
- We now detect and correctly synchronise file moves where the destination already existed and is being overwritten. However since filesystems and file browsers are all different, you might have a different experience on Linux. We made sure this works with the GNOME file browser, Nautilus.
- We improved the way we aggregate quick modifications to files to avoid having to synchronise a lot of changes when we only care about the result of the last one.
See also known issues.
Happy syncing!
Improvements for Windows and GNU/Linux users:
- We recently fixed an issue we had in the generation of a conflict file name where the conflict suffixes could be added indefinitely in case the conflicting file would get in conflict again. It happens that directories are still subject to a similar issue. We made sure directories will only ever have one conflict suffix added to their name event in case they get in conflict again.
- During the synchronisation process, a document can change either locally (e.g. its checksum has changed because of a modification) or on the Cozy (e.g. the file was moved or modified by another client). In this situation the Cozy won't accept the change and will answer with an error. When we receive errors from the Cozy we retry up to 3 times to apply the change but if the document has changed, we will never be able to apply it and will only lose time by retrying. We now retry only on network and disk space errors to speed up the synchronisation of files rapidly changing.
See also known issues.
Happy syncing!
Improvements for Windows and GNU/Linux users:
- Rapid successive changes on the same file were possibly generating conflicts because the new watcher was messing up with the changes propagation. There were actually 2 underlying issues behind this: one that was specific to the new watcher and another that was not. We actually fixed both, although the second one was not supposed to happen anymore once the new watcher would behave correctly, but could still have been uncovered during upcoming optimizations.
See also known issues.
Happy syncing!
Improvements for Windows users:
- With the new local watcher, we introduced a more precise way to identify files and folders on the filesystem. To make sure previously detected documents benefit from this new identification we need to migrate all of them when we get the new identifier. This version takes care of the migration in a way that avoids running a full synchronisation when we only change the identifier as it has value on the local client only.
There are some known issues that we'll tackle in the next releases:
- On Windows, moving a tree of directories and files to a destination that
shares part of this tree (e.g.
src/dir/subdir/file→dst/dir/subdir/file) and overwriting the destinations will result in conflicts being created for the overwritten files. - On Windows, the synchronisation of a remote move stopped before it's been applied on the local system will won't be resumed when restarting the client.
- On Linux, some movements done while the client was stopped won't be correctly detected and handled when starting the client.
See also known issues.
Happy syncing!
Improvements for Windows and Linux users:
- The new local watcher is now the default watcher. It should bring better performance in local changes analysis.
- We found a bug in the synchronisation process of directories that could lead to missed updates. We have not seen any reports of it but the mechanism has been fixed anyway.
- We updated one of our main dependencies, Electron, to its 2.x version. We are still not using the latest version but this one brings us back support from the Electron team and security fixes. Other updates will come in the following releases.
Improvements for Windows users:
- Files and folders named like a volume (e.g. C:) and at the root of the folder watched by Cozy Desktop could lead to an infinite loop if they or any of their children were ever modified. Those are now handled properly and won't be ignored either.
There are some known issues that we'll tackle in the next releases:
- On Windows, moving a tree of directories and files to a destination that
shares part of this tree (e.g.
src/dir/subdir/file→dst/dir/subdir/file) and overwriting the destinations will result in conflicts being created for the overwritten files. - On Windows, the synchronisation of a remote move stopped before it's been applied on the local system will won't be resumed when restarting the client.
- On Linux, some movements done while the client was stopped won't be correctly detected and handled when starting the client.
See also known issues.
Happy syncing!
Improvements for Windows users:
- Changing only the case of a file/directory name now works as expected when using the new watcher.
See also known issues.
Happy syncing!
Improvements for Windows and Linux users:
- Successive moves (e.g. A → B → C → D) are now correctly applied (i.e. A → D) with the new local watcher.
- The introduction of the new local watcher brought a performance regression during the initial Cozy directory scan. We ported an optimisation we had in the previous watcher to the new one which should make the initial scan phase about 3x faster.
- We found a bug in the synchronisation process of directories that could lead to missed updates. We have not seen any reports of it but the mechanism has been fixed anyway.
- We updated one of our main dependencies, Electron, to its 2.x version. We are still not using the latest version but this one brings us back support from the Electron team and security fixes. Other updates will come in the following releases.
Improvements for Windows users:
- Moves from a directory that has just been moved to a path outside this directory will now be correctly detected and applied with the new local watcher.
There are some known issues that we'll tackle in the next releases:
- On Windows, moving a tree of directories and files to a destination that
shares part of this tree (e.g.
src/dir/subdir/file→dst/dir/subdir/file) and overwriting the destinations will result in conflicts being created for the overwritten files. - On Windows, the synchronisation of a remote move stopped before it's been applied on the local system will won't be resumed when restarting the client.
- On Linux, some movements done while the client was stopped won't be correctly detected and handled when starting the client.
See also known issues.
Happy syncing!
Improvements for Windows and Linux users:
- The new local watcher is now the default watcher. It should bring better performance in local changes analysis.
Improvements for Windows users:
- Files and folders named like a volume (e.g. C:) and at the root of the folder watched by Cozy Desktop could lead to an infinite loop if they or any of their children were ever modified. Those are now handled properly and won't be ignored either.
There are some known issues that we'll tackle in the next releases:
- On Windows, moving the child of a moved directory won't be handled properly.
- On Windows, moving a tree of directories and files to a destination that
shares part of this tree (e.g.
src/dir/subdir/file→dst/dir/subdir/file) and overwriting the destinations will result in conflicts being created for the overwritten files. - On Windows, the synchronisation of a remote move stopped before it's been applied on the local system will won't be resumed when restarting the client.
- On Linux, some movements done while the client was stopped won't be correctly detected and handled when starting the client.
See also known issues.
Happy syncing!
Improvements for Windows and Linux users:
- The watcher type used (i.e. atom or chokidar) can now be chosen via the config file. This means the new watcher will be testable easily with any version of the app starting from now.
See also known issues.
Happy syncing!
Notice: This release uses the new watcher by default on Windows and GNU/Linux for testing purpose only and should not be used in other situations.
Improvements for all users:
- Fixed a race condition case were a sharing could be disabled when a folder was moved locally while another one was added remotely to the same destination.
Improvements for Windows and Linux users:
- The right path separator is now used while squashing successive events (e.g. file added or updated, then moved immediately) in the new watcher.
See also known issues.
Happy syncing!
Improvements for all users:
- We've improved the way we handle the revision of newly detected documents that are created at paths that have already been synchronised in the past. This was a potential source of conflicts were you to modify the content of such file.
- When moving a folder locally then quickly changing the content of a subfile on the same device, the file content may not be updated in the Cozy in some cases. Everything should now work as expected.
- We keep track of the changes made to documents to synchronise either with the remote Cozy or the local filesystem using version numbers for each side of the synchronisation. When moving a document, be it either a directory or a file, on the local filesystem as part of its parent directory move, the new local version number would be false, resulting in a possible desynchronisation of content updates. We now make sure both the local and remote version numbers get reset in this situation so future updates will be synchronised in the right direction.
- We've modified the way we handle child documents updates so everything gets synchronised, even if a child update occurs quickly after its parent directory has been renamed.
- We found out that moving a file or a directory to a path that has already been used in the path then deleted could lead to irrelevant version numbers for the new document and in the end to unnecessary conflicts. We now correct our version numbers when this situation happens so future updates to the document are handled correctly.
Improvements for contributors:
- The developer documentation's design section has been updated with the reasons that led to the decision to create a new local watcher and diagrams explaining how it works on Windows and Linux.
See also known issues.
Happy syncing!
Improvements for all users:
- We've modified the way we handle child documents updates so everything gets synchronised, even if a child update occurs quickly after its parent directory has been renamed.
- We found out that moving a file or a directory to a path that has already been used in the path then deleted could lead to unrelevant version numbers for the new document and in the end to unnecessary conflicts. We now correct our version numbers when this situation happens so future updates to the document are handled correctly.
Happy syncing!
Improvements for all users:
- We keep track of the changes made to documents to synchronise either with the remote Cozy or the local filesystem using version numbers for each side of the synchronisation. When moving a document, be it either a directory or a file, on the local filesystem as part of its parent directory move, the new local version number would be false, resulting in a possible desynchronisation of content updates. We now make sure both the local and remote version numbers get resetted in this situation so future updates will be synchronised in the right direction.
Happy syncing!
Improvements for all users:
- When moving a folder locally then quickly changing the content of a subfile on the same device, the file content may not be updated in the Cozy in some cases. Everything should now work as expected.
Notice for Windows & GNU/Linux users:
- This beta release uses the old watcher implementation. The new one is only used by default in alpha releases. We're still actively testing and improving it to make it the default in stable releases!
Happy syncing!
Improvements for all users:
- The count of objects to be synchronised was always 1 with the new local watcher. We've fixed this so the count is accurate and decreases with each element successfully synchronised.
- In some situations, the detection of local changes could be stalling. We've adapted the watcher so it detects when it can start processing filesystem events.
Improvements for contributors:
- The developer documentation's design section has been updated with the reasons that led to the decision to create a new local watcher and diagrams explaining how it works on Windows and Linux.
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed the issue preventing the new watcher from working past the initial synchronisation folder scan.
See also known issues.
Happy syncing!
Improvements for all users:
- We've improved the way we handle the revision of newly detected documents that are created at paths that have already been synchronised in the past. This was a potential source of conflicts were you to modify the content of such file.
Improvements for Windows and Linux users:
-
We're testing a new implementation of our local changes watcher on Windows and Linux. This should bring performance gains, faster change detection and in fine better stability. Some bugs can be present and not all existing features are implemented yet though.
It is acitvated by default in this early build for testing purposes only and should not be used in other situations.
See also known issues.
Happy syncing!
See 3.11.2-beta.1 See 3.11.2-beta.2
Improvements for all users:
- We've improved the wording of the updater window so it says it's downloading the new version and displays the Cozy Cloud logo so you know what's being updated at first glance.
- If a directory is overwritten by a move on your Cozy, we would move it to the trash and, in some situations, after synchronising your local client, the directory would not be overwritten on your computer. We're now skipping the move to the trash and overwriting the directory.
- We've improved the conflict resolution after changes made to local files when
the client was stopped. In this situation, we would resolve the conflict on
the remote Cozy and end up renaming the local copy with the
-conflict-suffix and could overwrite its content with the remote content thus losing the latest local changes. We're now resolving the conflict locally, keeping the remote version untouched. This has the additionnal benefit of keeping shared files free from the-conflict-suffix. - A function we introduced in version 3.11.0 was responsible for an increase in false negatives for an invariant check, leading to errors being thrown and synchronisations blocked. We've reworked said function in a way that won't trigger false negatives for the invariant which will reduce the number of errors and thus block synchronisations.
See also known issues.
Happy syncing!
Improvements for all users:
- We've improved the conflict resolution after changes made to local files when
the client was stopped. In this situation, we would resolve the conflict on
the remote Cozy and end up renaming the local copy with the
-conflict-suffix and could overwrite its content with the remote content thus losing the latest local changes. We're now resolving the conflict locally, keeping the remote version untouched. This has the additionnal benefit of keeping shared files free from the-conflict-suffix. - A function we introduced in version 3.11.0 was responsible for an increase in false negatives for an invariant check, leading to errors being thrown and synchronisations blocked. We've reworked said function in a way that won't trigger false negatives for the invariant which will reduce the number of errors and thus block synchronisations.
See also known issues.
Happy syncing!
Improvements for all users:
- We've improved the wording of the updater window so it says it's downloading the new version and displays the Cozy Cloud logo so you know what's being updated at first glance.
- If a directory is overwritten by a move on your Cozy, we would move it to the trash and, in some situations, after synchronising your local client, the directory would not be overwritten on your computer. We're now skipping the move to the trash and overwriting the directory.
See also known issues.
Happy syncing!
See 3.11.1-beta.1 See 3.11.1-beta.2
Improvements for all users:
- Moving a file or a folder multiple times in a row, synchronising them all at once, ending on a path that was also an intermediary step (e.g. move document A to B to C to B) would result in the synchronisation of the movement of the file or folder to the last known path before the movement to the intermediary step path and the addition of a new copy of the file or folder at the path of the intermediary step (i.e. movement from A to C and addition of B). We now correctly interpret those successive movements (i.e. movement from A to B).
- Editing the content of a file just moved with one of its ancestor could lead
to the incorrect detection of a conflict with its remote couterpart. We're now
updating its content as expected and thus avoiding creating any
-conflicts-file.
See also known issues.
Happy syncing!
Improvements for all users:
- Editing the content of a file just moved with one of its ancestor could lead
to the incorrect detection of a conflict with its remote couterpart. We're now
updating its content as expected and thus avoiding creating any
-conflicts-file.
See also known issues.
Happy syncing!
Improvements for all users:
- Moving a file or a folder multiple times in a row, synchronising them all at once, ending on a path that was also an intermediary step (e.g. move document A to B to C to B) would result in the synchronisation of the movement of the file or folder to the last known path before the movement to the intermediary step path and the addition of a new copy of the file or folder at the path of the intermediary step (i.e. movement from A to C and addition of B). We now correctly interpret those successive movements (i.e. movement from A to B).
See also known issues.
Happy syncing!
See 3.11.0-beta.1 See 3.11.0-beta.2
Improvements for all users:
- We will now alert you when a new version of the app is available and give you the option of restarting it to download and apply the new version or postpone it.
- You now have the opportunity to force a manual synchronisation from the settings panel. This will be useful mostly to fetch some remote changes without waiting for the periodic pull.
- Being always careful when it comes to your data, trying our best not to
lose any of it, when we try to reconciliate changes, we try to figure out
if the two documents we're comparing are the same. We were a bit too
conservative on this side and a lot of changes could lead to false conflicts
because of this. We're now doing a smarter comparison which should lead to
a lot less
-conflict-documents being generated. - For the same reason, when it comes to conflicts we prefer to leave it to you
to choose between the two versions we detected. However, when it comes to
changes that haven't been synchronized yet, we can avoid creating a conflict
and pick the latest version for you. From now on, we won't create a
-conflict-version of a folder that has been changed locally and never synchronized remotely with your Cozy. - If a file was changed remotely and its parent folder moved or renamed, we could end up moving the file locally but not synchronize its new content. We're now synchronizing all those changes correctly, leaving you with an updated file in the correct location.
- Similarly, adding a file locally to a folder that was just renamed or moved but not yet fully synchronized with the remote Cozy would result in a situation where the file is never uploaded to the remote Cozy and any changes to it wouldn't be synchronized either. We're now making sure we finish synchronizing the folder change and then synchronize the newly added file.
See also known issues.
Happy syncing!
Improvements for all users:
- You now have the opportunity to force a manual synchronisation from the settings panel. This will be useful mostly to fetch some remote changes without waiting for the periodic pull.
- Being always careful when it comes to your data, trying our best not to
lose any of it, when we try to reconciliate changes, we try to figure out
if the two documents we're comparing are the same. We were a bit too
conservative on this side and a lot of changes could lead to false conflicts
because of this. We're now doing a smarter comparison which should lead to
a lot less
-conflict-documents being generated.
See also known issues.
Happy syncing!
Improvements for all users:
- We will now alert you when a new version of the app is available and give you the option of restarting it to download and apply the new version or postpone it.
- To avoid losing your data, we're very careful when it comes to conflicts and
we prefer to leave it to you to choose between the two versions we detected.
However, when it comes to changes that haven't been synchronized yet, we can
avoid creating a conflict and pick the latest version for you.
From now on, we won't create a
-conflict-version of a folder that has been changed locally and never synchronized remotely with your Cozy. - If a file was changed remotely and its parent folder moved or renamed, we could end up moving the file locally but not synchronize its new content. We're now synchronizing all those changes correctly, leaving you with an updated file in the correct location.
- Similarly, adding a file locally to a folder that was just renamed or moved but not yet fully synchronized with the remote Cozy would result in a situation where the file is never uploaded to the remote Cozy and any changes to it wouldn't be synchronized either. We're now making sure we finish synchronizing the folder change and then synchronize the newly added file.
See also known issues.
Happy syncing!
See 3.10.4-beta.1
Improvements for all users:
- When the app was stopped in the middle of a synchronization, with folder moves
coming from the remote Cozy, we could end up detecting conflicts on those
folders undefinitely after restarting it. We now handle unapplied moves upon
startup and avoid creating unnecessary
-conflicts-folders. - If a file existing both locally and in the remote Cozy was updated more than once without synchronization, the latest changes would create a conflict and its resolution would override the file with an older version leading to data loss. We now simply override the local version of the file with the latest changes and synchronize them with the remote Cozy.
See also known issues.
Happy syncing!
Improvements for all users:
- When the app was stopped in the middle of a synchronization, with folder moves
coming from the remote Cozy, we could end up detecting conflicts on those
folders undefinitely after restarting it. We now handle unapplied moves upon
startup and avoid creating unnecessary
-conflicts-folders. - If a file existing both locally and in the remote Cozy was updated more than once without synchronization, the latest changes would create a conflict and its resolution would override the file with an older version leading to data loss. We now simply override the local version of the file with the latest changes and synchronize them with the remote Cozy.
See also known issues.
Happy syncing!
See 3.10.3-beta.1 See 3.10.3-beta.2 See 3.10.3-beta.3
Improvements for all users:
- The app is now available in spanish. Huge thanks to our translation contributors, especially Hernando ❤️
- Files and directories can now only have one
-conflict-...suffix at a time. Existing ones with multiple suffixes won't be renamed automatically, but in case a new conflict occurs, their suffixes will be squashed into a single one with the new timestamp. Although this doesn't fix the root causes, it should make the symptom easier to deal with. We're sill investigating the underlying issues. Expect more fixes soon. - We fixed a couple of issues preventing user-defined ignore rules to be loaded.
- Files moved right after they've been added to the Cozy folder and before we've had the chance to upload them will be synchronized anyway, at the right path.
- When a folder was moved on the Cozy or another device, the metadata of some of its content was not updated properly, although the content was effectively moved to the right place. Subsequent updates to these subfolders & subfiles could then trigger unexpected conflicts. This should now work as expected. (#1274)
- When a file was effectively edited on 2 devices and the local one was detected first, both were mistakenly renamed with a conflict suffix. Now only one of them will be renamed. (#1285)
See also known issues.
Happy syncing!
Improvements for all users:
- When a folder was moved on the Cozy or another device, the metadata of some of its content was not updated properly, although the content was effectively moved to the right place. Subsequent updates to these subfolders & subfiles could then trigger unexpected conflicts. This should now work as expected. (#1274)
- When a file was effectively edited on 2 devices and the local one was detected first, both were mistakenly renamed with a conflict suffix. Now only one of them will be renamed. (#1285)
See also known issues.
Happy syncing!
Improvements for all users:
- Files moved right after they've been added to the Cozy folder and before we've had the chance to upload them will be synchronized anyway, at the right path.
See also known issues.
Happy syncing!
Improvements for all users:
- The app is now available in spanish. Huge thanks to our translation contributors, especially Hernando ❤️
- Files and directories can now only have one
-conflict-...suffix at a time. Existing ones with multiple suffixes won't be renamed automatically, but in case a new conflict occurs, their suffixes will be squashed into a single one with the new timestamp. Although this doesn't fix the root causes, it should make the symptom easier to deal with. We're sill investigating the underlying issues. Expect more fixes soon. - We fixed a couple of issues preventing user-defined ignore rules to be loaded.
See also known issues.
Happy syncing!
See 3.10.2-beta.1
Improvements for all users:
- We fixed a couple of issues where a temporary file and an updated/overwritten one (both typically generated by office suites) were mistakenly identified as a move/renaming.
- We also fixed a small offline/online flashing status issue.
Improvements for Windows users:
- In case your synchronized directory is on a separate volume, the Windows
recycle bin (
$Recycle.Bin) folder is now properly ignored.
Improvements for contributors:
yarn installnow only installs npm dependencies: no more electron rebuild nor elm packages install.yarn install:allcan be used instead for this.- Continuous integration & publication are faster (more on Windows soon).
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed a couple of issues where a temporary file and an updated/overwritten one (both typically generated by office suites) were mistakenly identified as a move/renaming.
- We also fixed a small offline/online flashing status issue.
Improvements for Windows users:
- In case your synchronized directory is on a separate volume, the Windows
recycle bin (
$Recycle.Bin) folder is now properly ignored.
Improvements for contributors:
yarn installnow only installs npm dependencies: no more electron rebuild nor elm packages install.yarn install:allcan be used instead for this.- Continuous integration & publication are faster (more on Windows soon).
See also known issues.
Happy syncing!
See 3.10.1-beta.1
Improvements for all users:
- We fixed handling of connection loss. The Cozy Drive client will now correctly display when it's offline and re-attempt synchronization regularly.
- We improved the way we save the configuration file and gracefully recover if the configuration file is incorrect.
- Some text, translations and styles updates on the user interface
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed handling of connection loss. The Cozy Drive client will now correctly display when it's offline and re-attempt synchronization regularly.
- We improved the way we save the configuration file and gracefully recover if the configuration file is incorrect.
- Some text, translations and styles updates on the user interface
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed a couple of harmless issues occuring after syncing a move locally. (see 3.10.0-beta.4)
- We fixed an issue occuring when the destination of a file or directory moved on one side was already existing on the other side. The conflict is now properly resolved. (see 3.10.0-beta.3)
- Renaming directories a to c then b to a was working for files but not for directories. This now works for simple cases. A few complex ones are still not working however. (see 3.10.0-beta.1)
- In some very rare cases where the content of a file in the Cozy doesn't match the correct checksum, the app will check the local file version and reupload it when relevant. (see 3.10.0-beta.1)
- Starting from now, we will be able to automatically receive notifications of errors encountered by our users. Error reports won't include user logs in order to respect your privacy. We'll still have to ask you individually to send us our logs in order to investigate complex issues. But this should help us figuring out which errors occur the most, since not so many people can find the time to report them. For now, the notifications are only sent for a few hard-to-investigate issues, but we'll progressively send more of them. (see 3.9.1-beta.4)
- Checksums for new local files were computed but not sent during the initial upload, possibly delaying detection of content issues. Still the checksum was computed by the Cozy and any issue would've be detected during next polling. They will now be effectively detected as soon as they should be. (see 3.9.1-beta.4)
- Moves overwriting the destination performed on another device should now be synchronized as expected. (see 3.9.1-beta.2)
- Some part of the synchronization engine dating back to Cozy v2 was not necessarily preventing local directory of file overwrites. This part was reworked to reach the same level as the other ones, possibly fixing a couple of bugs. (see 3.9.1-beta.2)
- We noticed that synchronizing a local file update to the Cozy could fail in some very rare cases. We added a few automatic verifications which should help us narrow the issue, so hopefully we'll be able to definitely fix it in another release. (see 3.9.1-beta.2)
- Fix synchronization bugs when merging and overwriting folders. (see 3.9.1-beta.1)
Improvements for Windows & macOS users:
- When renaming a remote directory by only changing its case, the change was applied locally but it was also triggering a weird synchronization loopback error. This should now work as expected. (see 3.10.0-beta.1)
- Making the whole or some filename part upper/lower case used to be notably unsupported. It should now work everywhere. (see 3.9.1-beta.2)
- When two files and/or directories with only upper/lower case differences in their names are coexisting on your Cozy, only one of them will be synchronized locally on your case-preservative OS and the other one will be renamed as a conflict so you at least have a way to end up with the exact same tree on your Cozy and all your devices. (see 3.9.1-beta.2)
Improvements for Windows users:
- A few users reported that the app couldn't read its configuration anymore,
while it used to work. Although were still investigating the issue, the app
will now properly warn the user and take her back to the onboarding. We'll
soon come up with a way to write the configuration to prevent a theoretically
possible issue. Please report to us in case you're still affected (especially
including whether or not you opened your
.cozy-desktop/config.jsonfile with some third-party application). (see 3.10.0-beta.3) - Files made (non-)executable on another macOS or GNU/Linux device were triggering useless synchronization cycles (or conflict in the worst case). This should now work as expected. (see 3.9.1-beta.2)
Improvements for macOS users:
- On devices automatically migrated from HFS+ to APFS while upgrading to macOS High Sierra, the initial scan was mistakenly detecting some files as conflict due to the new way we're detecting case/encoding conflicting files. This should now work as expected. This issue could theoretically have happened on both macOS & Windows in rare cases of weird local filename changes. (see 3.9.1-beta.4)
- A regression on folder moves overwriting their destination was fixed (#1181) (see 3.9.1-beta.3)
- Better support for APFS (see 3.9.1-beta.1)
Improvements for macOS and GNU/Linux users:
- Local files made non-executable will now effectively be synced as non-executable on the Cozy and your other devices. (see 3.9.1-beta.2)
- Please note that currently the permissions of your local files may be forced to 755 or 644, depending on the executable status. However this should not be a major issue, unless your made both your personal directory and your Cozy Drive directory accessible to other users on your device. We'll definitely come up with a better solution at some point to make the executable bits match your existing local read/write ones. (see 3.9.1-beta.2)
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed a couple of harmless issues occuring after syncing a move locally.
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed an issue occuring when the destination of a file or directory moved on one side was already existing on the other side. The conflict is now properly resolved.
- In 3.10.0-beta.1 we introduced automatic reupload of content mismatching files. This actually relies upon a recent cozy-stack feature. Old stacks lacking the feature were not handled gracefully. Reupload is now properly disabled for old stacks.
Improvements for Windows users:
- A few users reported that the app couldn't read its configuration anymore,
while it used to work. Although were still investigating the issue, the app
will now properly warn the user and take her back to the onboarding. We'll
soon come up with a way to write the configuration to prevent a theoretically
possible issue. Please report to us in case you're still affected (especially
including whether or not you opened your
.cozy-desktop/config.jsonfile with some third-party application).
See also known issues.
Happy syncing!
Improvements for all users:
- We fixed an issue introduced by the recent case/encoding handling changes.
See also known issues.
Happy syncing!
Improvements for all users:
- We introduces automatic error notifications in 3.9.4-beta.1, but a few errors were actually not sent. They're effectively sent now.
- Renaming directories a to c then b to a was working for files but not for directories. This now works for simple cases. A few complex ones are still not working however.
- In some very rare cases where the content of a file in the Cozy doesn't match the correct checksum, the app will check the local file version and reupload it when relevant.
Improvements for Windows & macOS users:
- When renaming a remote directory by only changing its case, the change was applied locally but it was also triggering a weird synchronization loopback error. This should now work as expected.
See also known issues.
Happy syncing!
Improvements for all users:
- Starting from now, we will be able to automatically receive notifications of errors encountered by our users. Error reports won't include user logs in order to respect your privacy. We'll still have to ask you individually to send us our logs in order to investigate complex issues. But this should help us figuring out which errors occur the most, since not so many people can find the time to report them. For now, the notifications are only sent for a few hard-to-investigate issues, but we'll progressively send more of them.
- Checksums for new local files were computed but not sent during the initial upload, possibly delaying detection of content issues. Still the checksum was computed by the Cozy and any issue would've be detected during next polling. They will now be effectively detected as soon as they should be.
Improvements for macOS users:
- On devices automatically migrated from HFS+ to APFS while upgrading to macOS High Sierra, the initial scan was mistakenly detecting some files as conflict due to the new way we're detecting case/encoding conflicting files. This should now work as expected. This issue could theoretically have happened on both macOS & Windows in rare cases of weird local filename changes.
See also known issues.
Happy syncing!
Improvements for macOS users:
- A regression on folder moves overwriting their destination was fixed (#1181)
See also known issues.
Happy syncing!
Improvements for all users:
- Moves overwriting the destination performed on another device should now be synchronized as expected.
- Some part of the synchronization engine dating back to Cozy v2 was not necessarily preventing local directory of file overwrites. This part was reworked to reach the same level as the other ones, possibly fixing a couple of bugs.
- We noticed that synchronizing a local file update to the Cozy could fail in some very rare cases. We added a few automatic verifications which should help us narrow the issue, so hopefully we'll be able to definitely fix it in another release.
Improvements for Windows and macOS users:
- Making the whole or some filename part upper/lower case used to be notably unsupported. It should now work everywhere.
- When two files and/or directories with only upper/lower case differences in their names are coexisting on your Cozy, only one of them will be synchronized locally on your case-preservative OS and the other one will be renamed as a conflict so you at least have a way to end up with the exact same tree on your Cozy and all your devices.
Improvements for macOS and GNU/Linux users:
- Local files made non-executable will now effectively be synced as non-executable on the Cozy and your other devices.
- Please note that currently the permissions of your local files may be forced to 755 or 644, depending on the executable status. However this should not be a major issue, unless your made both your personal directory and your Cozy Drive directory accessible to other users on your device. We'll definitely come up with a better solution at some point to make the executable bits match your existing local read/write ones.
Improvements for Windows users:
- Files made (non-)executable on another macOS or GNU/Linux device were triggering useless synchronization cycles (or conflict in the worst case). This should now work as expected.
See also known issues.
Happy syncing!
Improvements for all users:
- Fix synchronization bugs when merging and overwriting folders.
Improvements for macOS users:
- Better support for APFS
See also known issues.
Happy syncing!
Improvements for all users:
- Improved timestamp conflict handling (see 3.9.0-beta.1)
- New diff-based data comparison algorithm (see 3.9.0-beta.1)
- Improved file move + overwrite handling (see 3.9.0-beta.2)
- New TOS update dialog (see 3.9.0-beta.2)
Improvements for Windows & macOS users:
- Initial scan properly ignores platform-incompatible remote files (see 3.9.0-beta.1)
Note for GNOME 3.28 or later users:
- Better use TopIcons, not TopIcons-Plus (see 3.9.0-beta.1)
See also known issues.
Happy syncing!
Improvements for all users:
- Moving a file to overwrite an existing one is now effectively synchronized as expected.
- Users don't look at the systray popover so often. So people who have not accepted the new TOS may be unaware that the synchronization is currently paused. The app now shows up a reminder dialog on start when appropriate.
See also known issues.
Happy syncing!
Improvements for all users:
- When a file or directory exists in the cozy, the app will never try to assign it an older timestamp anymore. This will ensure synchronization still works, even when the local timestamp is actually more accurate than the remote one. We'll later introduce a way to save the correct timestamp without being rejected by the Cozy.
- The data comparison algorithm is now diff-based. This will help us investigate a very rare (but hard to fix) bug where a file is detected as modified while no change is actually visible.
Improvements for Windows & macOS users:
- When a file or directory couldn't not be synchronized locally because of some platform incompatibility (e.g. reserved character), it will be properly ignored during initial scan after restarting the app.
Improvements for support:
- Summarized and detailed traces are now always stored together to make analysis easier.
Note for GNOME 3.28 or later users:
- You may have to switch from TopIcons-Plus back to good old TopIcons in case the app doesn't show up when clicking on the tray icon, whatever the app version.
See also known issues.
Happy syncing!
There was no 3.8.0 stable release since we had to release a 3.8.1-alpha first. So 3.8.1 is the first stable release since 3.7.0.
Improvements for all users:
- When a change could not be applied on the other side, the document was not considered up-to-date anymore on the source side. This was fixed as part of the 3.8.0-beta.1 release.
Improvements for Windows users:
- Office temporary files should be effectively ignored since 3.8.0-beta.1 too.
Improvements for macOS users:
- In macOS 10.13 (High Sierra), Apple removed the feature we were using to add the Cozy Drive directory to the Finder's favorite items. We had to find another way to bring it back. It should work as expected now.
Improvements for developers / contributors:
- One step less to build the app:
yarn build:coreis not needed anymore. If you were usingyarn build, it should work the same as before. But now you won't have to rebuild in case of a core change before running the GUI. Less dependencies. Shorter stacktraces. This also fixed a few oddities. - We also improved logs and jq filters.
See also known issues.
Happy syncing!
Improvements for all users:
- When a file could not be uploaded/downloaded that may generate conflicts when editing/saving a file multiple times.
- Ignored files (e.g. Office temporary files) should now be effectively ignored on Windows.
Improvements for Arch Linux users:
- You should now be able to install
cozy-desktopfrom community repo, courtesy of ArchangeGabriel. Huge thanks to him!
See also known issues.
Happy syncing!
Improvements for all users:
- Handle user action required and action completion
- Make Auto-Update Error Transparent
- Handle emptied folder
Please see the previous beta releases for more details. See also known issues.
Happy syncing!
Improvements for all users:
- The app should detect (may take between 5 seconds and 1 minute according to elapsed time between click inside the app and completion) when required user action has been completed (i.e. new TOS validation) and restart automatically.
Improvements for developers:
- New jq file extension/gui/issues filters for logs
See also known issues.
Happy syncing!
Improvements for all users:
- The app won't display an error in case of an auto-update failure. Errors are logged anyway and auto-update will be retried automatically at some point.
Improvements for developers:
- Developers won't have to wait for the above error to disappear.
See also known issues.
Happy syncing!
Improvements for all users:
- The app now detects when the Cozy Drive folder was made empty while it used to have contents before. Synchronization is stopped. User can either restart later in case the folder is a mount point that was not available yet, or delete the root folder before restart to actually restart from scratch.
- Warnings from the Cozy instance (e.g. TOS updates) are now detected. A bottom banner is shown in the UI prompting the user to read the detail before the deadline. After the deadline, synchronisation is stopped and reading the detail will be mandatory.
- We also fixed an issue that was preventing some errors to be correctly written in logs.
Improvements for developers:
- Logs are dumped on failing test (will help debugging random CI issues)
- Upgrade to Go 1.9 & Couchdb 2.1 on Travis CI
See also known issues.
Happy syncing!
See:
See also known issues.
Happy syncing!
Improvements for all users:
- Moved & renamed files are now listed in the Recents tab.
Improvements for Windows users:
- Starting from this beta release, the app should be signed with our renewed certificate.
See also known issues.
Happy syncing!
Improvements for all users:
- The Recents tab is now clearer and more reliable.
- The app will suggest sending support requests from each desktop device you own so we can pinpoint multi-device issues.
Improvements for developers & support team:
- You can now filter log entries on multiple path fields (e.g.
yarn jq 'filter_path("pattern")') - User-sent logs archive extension now matches the actual format.
- Logs also include less noise.
See also known issues.
Happy syncing!
Improvements for all users:
- The app won't poll the Cozy anymore when descendant synchronization is already in progress.
- Errors occurring during auto-update are now properly reported to the user, with a generic message by default and a more specific one whenever possible (e.g. permission issue or disk full).
- The app also properly waits for dir trashing to succeed (issue introduced in 3.6.0-beta.1).
- The icon used in the systray window header is now the official blue one on Windows and GNU/Linux (we still use the symbolic icon on macOS since it integrates better with the overall desktop environment).
Improvements for Windows users:
- We set up a temporary workaround for a bug in electron that is preventing notifications to show up on Windows.
Improvements for i3wm (and possibly other tiling window managers) users:
- You can now force an option so the systray Window stays visible when loosing focus (please look at the GNU/Linux documentation for more details). Please tell us whether or not it also helps with other tiling window managers.
See also known issues.
Happy syncing!
Improvements for all users:
- The app won't recompute the checksum of a file when its last modification date has not changed.
See also known issues.
Happy syncing!
Improvements for all users:
- Electron was upgraded from 1.7.9 to 1.8.3 (including quite a few security and bug fixes).
- The file/directory move synchronization logic (the part that takes
already-merged metadata changes and turn them into actions on the other side)
was substantially rewritten to make it more robust and handle more complex
cases (e.g. moving
a/tob/thenc/toa/, or movinga/tob/then deletingb/). - A file won't be updated when only its mtime changed. This is a first necessary step to later stop computing checksums for files with unmodified mtime, making the initial scan faster.
Improvements for macOS and BSD users:
- We fixed a weird recurring error that was generating useless logging on every run.
Improvements for developers and support team:
- ES6 modules were replaced with node.js ones. This is a first necessary step to get rid of Babel, simplify our build process and make stacktraces smaller and easier to read.
- The app now waits for the configuration to be loaded before logging full client information (not just some part of it).
- We introduced a few jq filters to help filtering huge logs. Those should work well with multiple huge log files (e.g. > 1GB).
This is the same release as 3.5.0-beta.4, but the version has been updated.
Main changes:
- Improved upload reliability
- Files and folders with name starting with a
.are now ignored by default. If this is an issue for you, please contact us and explain your use case. - Support requests from the app now uploads your logs directly to our servers.
- When a platform-incompatible folder name is fixed, its files are synced too.
- You can choose to sync a non-empty folder.
- You can exit without confirming unattended revocation and try again later.
- We added traces to spot weird blank page issue on Windows, please try with this new release and send us your logs.
And more... See previous beta releases for more details:
See also known issues.
Happy syncing!
Improvements for all users:
- Files and folders with name starting with a
.will now be ignored by default. We used to blacklist a few special hidden files and folders, but it didn't prove an efficient way to prevent unsupported use cases and issues. So we decided to go the opposite way. Please report specific issues with as many context as possible so we can understand the actual need. - When sending a support request from the app, your logs are now uploaded directly to our own servers. They're not sent by email anymore, so it should work even with huge files (although the upload may take some time).
- The app now detects and handle a few file and folder deletion events miscategorized by a third-party component (very rare bug).
- A few users where looking for the CLI, not knowing it was actually disabled. The documentation was updated to reflect this.
Improvements for Windows and macOS users:
- When taking a folder with a platform-compatible name, renaming it with a platform-incompatible name then renaming it back to a compatible one, files were still not synced back (it worked in other cases though). This issue is fixed now.
Improvements for Windows users:
- We added UI traces to help us spot a weird issue: at least 2 Windows users recently reported blank windows when starting the app (at least one of them solved the issue by switching to automatic video card selection, but we're still investigating). In case you encountered this issue, please try again with this new release and send us a support request from the app.
See also known issues.
Happy syncing!
Improvements for all users:
- A lot of desktop clients were disconnected recently. Although it seems the issue is not on the app side, users were forced to disconnect, go through the onboarding steps again, and synchronize there whole drive back. The latest stable release (v3.4.5) allowed selecting a non empty synced directory to lower the impact of this issue. This new beta release allows user to exit the app from the revocation notification dialog without actually disconnecting and try synchronizing again later.
We apologize for the inconvenience.
Improvements for all users:
- All dual-screen window positioning issues should be fixed.
Improvements for macOS users:
- Notifications used to be quite broken on macOS. Everything should just work now.
- Special
Icon\rfiles were not properly ignored during synchronization, probably due to a weird bug in some third-party component. Although it could make sense to synchronize them between 2 macOS computers, the cozy-stack actually doesn't support creating a file with name containing a\rcharacter. We made sure those files were properly ignored.
Improvements for developers:
- Test reports recently stopped working when run with coverage enabled (e.g. on CI). Everything is back to normal.
See also known issues.
Happy syncing!
Improvements for KDE users:
- the icon is now correctly sized, thanks to @hleroy
Improvements for all users:
- File uploads are now made with
Content-Lengthinstead ofTransfer: chunkedwhich should improve stability.
See also known issues.
Happy syncing!
Improvements for all users:
- Allow selection of an non-empty sync dir as a quickfix following the 26/02 forced logout production incident.
The 3.4.4 build was broken.
Also include all changes from 3.4.4-beta.1, 3.4.4-beta.2 and 3.4.3-beta.3.
See also known issues.
Happy syncing!
Improvements for all users:
- We added more traces and test cases to help us fix popover positioning issues. Please send us a message from the app in case you encounter an issue, so we can get your traces and understand your specific case.
Improvements for macOS users:
- Make sure the popover at least shows up to the top right when the reported tray icon position is broken (as it seems to happen from time to time).
Improvements for GNOME 3 + Wayland users:
- Show the popover near the top icon, not at the bottom of the screen.
Improvements for KDE users:
- Fix issue preventing the popover to show up when clicking the systray icon on KDE (@hleroy)
Improvements for developers & contributors:
- Use unique user agent per client instance, so we can know how many people are actually using it.
- Instructions to set up a development environment on Ubuntu (@hleroy)
Improvements for all users:
- The remaining files counter didn't update anymore when encountering a synchronization error. Everything should work as expected now.
- We also fixed a couple of issues regarding the popover positioning. It should now properly detect the systray position and orientation. Please tell us in case the popover still shows up at weird locations on your desktop.
- We were using a temporary fix for some third-party component to make sure auto-update was working on Windows. The issue was fixed upstream and the component upgraded. Please tell us in case you still encounter auto-update issues, especially on Windows.
See also known issues.
Happy syncing!
Improvements for all users:
- When creating a folder with some platform-incompatible character in the name
(e.g.
:), then renaming to a valid name, its content is now correctly synchronized.
See also known issues.
Happy syncing!
Improvements for all users:
- Added more logs to better debug performance and compatibilities issues.
- All improvements from 3.4.3-beta.1
See also known issues.
Happy syncing!
Improvements for all users:
- During onboarding, you can now copy whatever URL from your browser pointing to your Cozy-hosted instance and paste it as your Cozy address in the configuration window. When submitted, the application will identify the corresponding Cozy address and remove the useless parts for you. Please tell us in case you find an URL that doesn't work. Also please note that there is no such automation for self-hosted users for now.
- You'll get quicker visual feedback when trying to select a non-empty directory as your synced location.
- In some rare cases, users ended up with a few files improperly uploaded to their Cozy. Those files were never considered up-to-date by the app, triggering useless synchronization cycles. They will now be detected and not synchronized indefinitely. Final work to improve upload reliability is planned for week 7 or 8.
- Support requests sent from the help form will now include more debugging and benchmarking information (including the application & OS versions). Please note debugging information only include filenames as usual, and benchmarking information only include time spent on various operations. This will help us to improve the overall performances.
- The documentation now lists the supported Windows and macOS versions. Work was previously done on the GNU/Linux side.
- An issue was fixed were the application was trying to put the focus
Improvements for GNU/Linux users:
- The application now tries to detect and display a user-friendly message when the system glibc is too old to run properly. Please note we may possibly try to lower the bar regarding the required version at some point.
See also known issues.
Happy syncing!
Improvements for all users:
- Synchronization & a few performance improvements
- Starting the app when already running will show the popover
- The Cozy configuration should be more user-friendly (including automatic address correction)
- Better support for Windows/macOS workspaces
- And more... Please see the beta releases for more details.
See also known issues.
Happy syncing!
Improvements for all users
- Improvements on synchronization, especially for moves or when changing files on both sides.
Improvements for early adopters with old Cozy instances:
- Recover when Cozy contains invalid data
Improvements for GNU/Linux users:
- We are progressively listing supported distributions.
Improvements for developers:
yarn replworks again, with usefulhelpers, also introducedyarn cozy-stack.
See known issues.
Happy syncing!
Improvements for Unity users:
- You can now open the application from the tray icon.
Improvements for all users:
- Attempting to restart the application will open the popover.
- Improve the design of error case on Cozy address wizard step.
- Minimal performance improvements. More soon!
See known issues.
Happy syncing!
Improvements for all users:
- To mitigate performance issues, we temporarily prevented choosing a non-empty directory to synchronize.
- Heuristic-based Cozy address correction
See known issues.
Happy syncing!
Improvements for all users:
- The onboarding includes a few more improvements for people not familiar with URL.
- We fixed an issue that prevented disconnecting the app from the Cozy.
Improvements for Windows users:
- Files checksum computation will be retried a few times when file is busy.
See known issues.
Happy syncing!
Improvements for all users:
- The app should now log and recover from remote files with an invalid parent directory. This issue was happening rarely and only on old Cozy instances.
- Showing up the popover near the systray could fail in rare cases for unknown reasons. We temporarily fixed the issue by falling back to showing the popover in the middle of the screen. Please send us a support request from the app in case it happens to you, so we can get all the information we were missing to fix it for good.
See known issues.
Happy syncing!
Improvements for all users:
- The app now shows the popover on the current workspace.
- We fixed an edge case where moving files or folders before or after moving their source or destination was generating a conflict.
- We also fixed another case where a folder created or moved locally could end up with the wrong last modification date.
See known issues.
Happy syncing!
Improvements for all users:
- It was possible in some specific cases to mess up the synchronization by moving around files & folders during the analysis phase. This is fixed now. Feel free to move everything around anytime :)
- In some cases, moving then immediately deleting a file was handled as 2 distinct actions. The file is now directly detected as deleted.
- The Cozy address page shown during onboarding should now be clearer for people not familiar with URL.
- When disconnecting then reconnecting to your Cozy, you could eventually see your old files for a few seconds in the dashboard. The fix was published in an old minor release, but not properly integrated to the subsequent releases. This is fixed now.
Improvements for support team & developers:
- Support requests from the app are now sent to the usual support email.
- Code coverage is back
See known issues.
Happy syncing!
See 3.4.1-beta.1 and 3.4.1-beta.2 release notes.
Happy syncing!
Improvements for all users:
- Fix weird packaging issue (detail)
Known issue for GNU/Linux users:
- The systray icon may appear twice (with only one icon actually working). Workaround: quit and restart. This should not happen on subsequent updates.
Happy syncing!
Improvements for all users:
- Deleting the synchronization folder will not trash all files on the cozy.
Changes for technical users (contributors, packagers, CLI users):
- Builds are now made in CI, which will allow us to quickly send patched versions for specific issues before they make it to the master, as well as quicker testing, so hopefully quicker releases.
See known issues.
Happy syncing!
Improvements for all users:
- The new quit button now appears busy once clicked.
- We added a missing french translation for the new message showing when selecting your whole system or personal folder to be synced.
Changes for technical users (contributors, packagers, CLI users):
- We moved to a new flat repository layout: single npm package, single runtime (electron), single node version (the electron one). This is a first step to make development easier and faster. The CLI & code coverage support are temporarily disabled. We should bring them back at some point, although the CLI will probably depend on the electron runtime for now.
See known issues.
Happy syncing!
Improvements for GNU/Linux users:
- Auto-update works!
- Auto-launch on system startup too!
- The application should now be visible as expected on alt+tab.
Improvements for all users:
- Invalid cozy address detection was improved, including automatic detection of
mycoSy.cloudwith ansinstead ofmycoZy.cloudwith az(which seems to be a common mistake). - The app also detects and prevent synchronizing your whole system or personal folder.
- Auto-update should be more reliable.
- The settings tab includes a new quit button.
See known issues.
Happy syncing!
Improvements for GNU/Linux users:
- First GNU/Linux release!
- Download the
*.AppImagefile, move it wherever you want, make it executable and run it. See details. - Since GNOME 3 doesn't have a systray anymore by default, you may need to install some third-party extension (e.g. TopIcons-Plus). See the dedicated section for remaining GNU/Linux integration issues.
Improvements for macOS users:
- The previous 3.3.1 fix regarding application visibility only worked when you had not pinned the Cozy Drive application in the dock. This should always work from now. See the dedicated section for remaining macOS integration issues.
Improvements for all users:
- We upgraded a major third-party component of the application, which may fix a few bugs related to the user interface (including the application hanging when started multiple times).
See known issues.
Happy syncing!
Improvements for all users:
- The Cozy Drive app now tries to automatically detect and use any configured
proxy (including authentication, i.e. Kerberos authentication shoud
just work).
We also added a few command-line options and environment variables to force
the configuration as needed:
--proxy-script path/to/your/script.pacorCOZY_DRIVE_PROXY_SCRIPT=path/to/your/script.pac--proxy-ntlm-domains '*example.com,*foobar.com,*baz'orCOZY_DRIVE_PROXY_NTLM_DOMAINS='*example.com,*foobar.com,*baz'to specify servers for which integrated authentication is enabled (use'*'for all servers).--login-by-realm 'realm1:login1:password1,realm2:login2:password2'orCOZY_DRIVE_LOGIN_BY_REALM='realm1:login1:password1,realm2:login2:password2'to pass credentials manually.--proxy-rules,--proxy-bypassrules,COZY_DRIVE_PROXY_RULESandCOZY_DRIVE_PROXYBYPASSRULESfor specifying which proxy should be used in which case (see details). Please tell us in case you still can't run the Cozy Drive app behind you proxy so we can support as many configurations as possible.
- We also fixed an edge case where simultaneous moves ended up with files in the Cozy / OS trash. Expect a few more fixes very soon.
Improvements for macOS users:
- The app is not visible anymore in the dock and with
Cmd+Tabwhen running in the background or showing the popover from the systray. It now behaves more like other systray-running apps. Also expect a few more fixes regarding systray integration.
Happy syncing!
Improvements for all users:
- Some miscellaneous style and translations fixes
See known issues.
Happy syncing!
Improvements for all users:
- Updates will now be detected automatically when starting Cozy Drive. When an update is available, a splash screen will ask you to wait while downloading (including the download progress on Windows only) and the app will restart automatically. When no update is available, the app will start as usual. Since the update check is quite fast, we decided to display a splash screen only during download, not while checking. In case of network issues, the app may take more time to start than usual, but it should still work.
- New revamped UI: the dashboard window was replaced with a popover showing up next to the (new) system tray icon. The synchronization status on top of the popover should give you more indications about what is actually occurring in the background. Navigation was simplified and moved to the top of the popover and the help form now shows up in its own separate window.
- Disconnecting the device from the Cozy or the app should work as expected now. Also since most people encountering issues were trying to reconfigure their device, we made sure logs were not deleted anymore in the process.
See known issues.
Happy syncing!
Improvements for all users:
- The synchronization now detects when remote files or directories were already deleted. details
- The remote Cozy overloading guard was disabled so the app doesn't hold on in case of synchronization errors. An improved version will be reenabled later. details
- The authorization screen should not be bigger than screen anymore. details
- Changing only case or encoding in a file or directory name won't trigger conflicts on other devices anymore. The case or encoding won't be synced though. We'll come up with a better solution at some point. details
See known issues.
Happy syncing!
It took us some time, but we're almost there, finally!
Improvements for all users:
- Moving or renaming shared directories should not break the sharing anymore.
- Moving or renaming connector directories should work as expected (the connector will put upcoming documents to the new location instead of recreating and filling up the old one).
- Moving or renaming a directory should now be more reliable, even with filesystem events occurring in random order as it seems to happen from time to time.
See known issues.
Happy syncing!
Improvements for all users:
- Fixed the styling of the Show more files button in the Dashboard screen.
- The default content of the support request form should now be translated properly.
Happy syncing!
Hello there! Sorry for the summer delay, the team took some rest, and recently we were quite busy working on some huge synchronization improvements, but that's for another story. So let's get back to the current release...
Improvements for all users:
- The onboarding (the successive screens where you configure Cozy Drive for Desktop on first launch) now follows the new Cozy v3 design guidelines and wording. The other screens were mostly updated too, especially the settings which were merged into a single tab. In future releases, the tabs should move to the top and we should progressively transition to a new popover layout sticking to your systray, instead of the current floating window. Some screens will still make use of a separate windows when relevant (e.g. the Help one).
- We also enlarged the Cozy login screen, the authorization screen (were you allow the Cozy Drive for Desktop app to access the data in your Cozy) and the Dashboard screen (the one showing recent updates). In case your display has a small resolution, the app should not exceed the available space and fall back to scrolling.
- The disk space gauge should now effectively match the available space.
- The app was occasionnaly crashing on startup with a weird db Lock error. This should not happen anymore. Please shout out loud in case it still does for you.
- We fixed an issue that was preventing errors to be properly notified when sending a support request from the Help screen. We also made sure that a favorite creation failure would not block the application.
- We now have traces of failures for almost everything in the app except for upgrades (which unfortunately seemed to be the source of issues recently, so we'll probably add it too). This should help us fix issues regarding the onboarding step for example.
- We also added some missing translations.
- Last but not least we added the hopefully last missing checks to detect conflicts while trashing/deleting folders from the Cozy.
Improvements for Windows users:
- Once configured, the app now adds a favorite to Windows 7 and Windows 8.x explorer.
- While uploading files from a Windows device, missing folders creation was failing. This is fixed now.
- We changed the way we hide some special folders on Windows. We extensively
checked it was working as usual on every supported Windows version, so this
should not be visible in any way for you. But in case you still start seing
some weird
.cozy-desktopor.system-tmp-cozy-drivedirectories, please tell us.
Happy syncing!
Improvements for all users:
- When creating folders and uploading files on the remote Cozy, sometimes the parent folder doesn't exist yet. This case didn't occur before the 3.0.0 release and it didn't happen during the release testing, so we were not handling it correctly. The issue is fixed now. We apologize for the inconvenience.
Happy syncing!
Improvements for all users:
- We improved support for unicode filenames for files already in your synchronization folder before starting cozy-drive
- Moved folders on your computer does not fill your cozy's trash.
- We fixed an issue preventing conflict resolution for a folder trashed on one side while content was added on the other side
Improvements for Windows users:
- When you first register your computer on the Cozy, the app will add your Cozy Drive folder to the Windows Explorer sidebar
- Both the installer and the application should now work on 32-bit Windows.
Happy syncing!
Improvements for Windows users:
- The Windows 10 cloud storage registration was disabled because it was not
stable enough yet. This means you won't get the
Cozy Driveshortcut in the Windows Explorer sidebar, near the OneDrive one. We'll come up with another solution, possibly compatible with older Windows releases. Please contact us in case you get stuck with broken shortcut(s) in your sidebar, we'll help you to fix it. We apologize for the inconvenience.
Happy syncing!
Improvements for all users:
- The application was renamed to Cozy Drive!
- Deleted files and folders on Cozy are now correctly synchronized on your computer.
- An infinite synchronization issue between multiple devices was fixed.
- Network load is now smaller when retrieving changes from the remote Cozy.
- Most useless copies of folders should not end up in the Windows recycle bin, the macOS trash or the Cozy trash anymore. Some issues remain though.
- Useless conflicts for trashed files/folders won't happen anymore (this was only visible in logs).
- Documentation was updated.
- Some typos in the french locale were fixed.
- We started adding more automated tests to prevent regressions and ensure a better quality for future releases.
Improvements for Windows 10 users:
- When you first register your computer on the Cozy, the app will add your Cozy Drive folder to the Windows Explorer sidebar (near the OneDrive one). If you disconnect from the settings, the sidebar shortcut will be removed.
Improvements for macOS users:
- When you first register your computer on the Cozy, the app will add your Cozy Drive folder to the Finder favorites. It will still have a normal folder icon though (same as the real folder). Also the favorite will not be removed when you disconnect. You can still easily remove it by hand. These small details should be fixed soon.
- The app will synchronize macOS folders without their custom icons (those are stored in hidden files with weird character in their name, which is not supported by the Cozy at the moment, and was triggering synchronization errors).
Improvements for all users:
- The temporary .cozy-desktop folder inside your Cozy Drive one was renamed to .system-tmp-cozy-desktop, to make sure even people displaying hidden files in their file browser won't try to put files in it and expect them to be synchronized.
- Logging improvements (for debugging purpose)
Happy syncing!
This is for testing purpose only. Do not install it, unless you know what you're doing.
Improvements for all users:
- You can now request support directly from the application.
- On the onboarding screen, you'll be warned in case you typed your email address instead of the address of your Cozy.
- The app will now start by default on login. You can still disable it in the settings.
- The activity indicator is now visible on deletions.
- Links are now opened in a new windows, so users don't end up with no way to get back.
- The content of a folder renamed offline will not be uploaded again.
- When a file was both updated locally and trashed remotely, it will be kept with the updated content.
- The app now enforces MD5Sum for all files, to ensure data consistency and to prevent weird issues.
- Disk space and revocation error messages should be clearer.
- Logs are easier to filter, which should help us to debug synchronization issues.
Improvements for Windows users:
- You should not see weird
.cozy-desktopdirectories anymore (including in your home and yourCozy Drivedirectories). - Fixed an issue with last modification date, which was preventing a file first uploaded through the Cozy Drive web app, then renamed locally, to be synced.
This is for testing purpose only. Do not install it, unless you know what you're doing.
Improvements for all platforms:
- When an update was available, the app used to display the version number and the release notes in the Settings. This was broken while migrating to the new auto-update system. The issue is partially fixed, but it only shows the summary instead of the full release notes for now.
- The auto-update migration also revealed another issue: the app was checking for updates every 1 or 2 minutes, triggering successive downloads of the latest release. This should work as expected now.
Improvements for Windows users:
- The app was not downloading updates from the appropriate location on Windows (while it was working on other platforms). This was fixed too.
Happy syncing!
This is for testing purpose only. Do not install it, unless you know what you're doing.
Improvements for all platforms:
- A beta release! Although some cases remain where synchronization breaks, it mostly works on all 3 platforms. Please report every issue!
- Switching to beta was good timing to change the version number format, which should finally fix the last auto-updates issue.
- The app will detect and prevent synchronization of files/folders with paths/names too long for your system, so you never end up with unusable content on your hard drive.
- When starting Cozy Desktop, it will detect an already running instance of the app, make it visible and exit (instead of displaying a weird error message).
Improvements for Windows users:
- The app now detects and displays using the user language.
Happy syncing!
This is for testing purpose only. Do not install it, unless you know what you're doing.
Improvements for all platforms:
- A new auto-updates system which should work better on both Windows and macOS
- Fixed an issue preventing a locally renamed file to be updated on the remote Cozy
Improvements for Windows users:
- The weird animation that was displayed while installing the app since the alpha4 release should be replaced with a normal install dialog.
Finally, we would like to apologize to our Windows users, since auto-updates actually didn't work in the alpha4 release. This should be fixed now. Thanks for your patience.
Happy syncing!
This is for testing purpose only. Do not install it, unless you know what you're doing.
Improvements for all platforms:
- Files are now synchronized to your Cozy Drive folder (to better match the Cozy Drive app name). If your already had a Cozy folder set up, Cozy Desktop will continue to use it. If you want to switch to the new folder, you can disconnect from your Cozy in the Settings, rename your local Cozy folder to Cozy Drive (so you don't need to download everything again), then restart Cozy Desktop, register and use the new folder.
- Your computer now appears in your Cozy as Cozy Drive (your computer name).
Improvements for Windows users:
- Installer and app are signed now, which should prevent warnings and allow us to support automatic updates. Since we use a standard certificate (not one with Extended Validation), you'll still get a confirmation popup at install time, until the app gets enough reputation in Microsoft SmartScreen (the anti-phishing system included in Windows 8 and later).
- This release (and upcoming ones) should now support automatic updates. But previous releases didn't, so you'll still have to download and install this one by hand.
- A third-party component used by Cozy Desktop to monitor your local folder was updated, fixing some issues on Windows.
Happy syncing!
This is for testing purpose only. Do not install it, unless you know what you're doing.
Improvements for all platforms:
- Restoring a folder from the Cozy trash is now supported.
- We fixed some conflict resolution issues. Creating / changing / restoring files with the same name should be more reliable now. Some issues remain, though.
- Most offline actions should work now, except for deletions.
Improvements for Windows users:
- A release! Getting a code signing certificate took more time than expected, though, so the app is not signed yet. This should be fixed in the next one.
- Windows file/dir paths are now supported, making the synchronization usable, hence the release.
- Files and folders with reserved name, reserved characters or terminating characters will not be synchronized locally and user will be warned.
Improvements for macOS users:
- The dock icon is now hidden when closing the Cozy Desktop window, so you don't see it with cmd-tab when running in background
- Files and folders with colon in their name will not be synchronized locally and user will be warned of this character as being reserved on macOS
This is for testing purpose only. Do not install it, unless you know what you're doing.
- Improve macOS packaging
- Improve conflict management
- Improve error management
- Improve log report
- Improve Windows support
This is for testing purpose only. Do not install it, unless you know what you're doing. Please note that future releases will only support the new Cozy stack v3.
- Proof of concept