# Disaster with Nexcloud 3.4.0 Client **URL:** \ **Category:** Existing Apps\ **Tags:** nextcloud\ **Created:** [27 December 2021 19:06 UTC](https://syncloud.discourse.group/t/disaster-with-nexcloud-3-4-0-client/141 "2021-12-27T19:06:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![janseta](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@janseta](https://syncloud.discourse.group/u/janseta)\ **Post date:** [27 December 2021 19:06 UTC](https://syncloud.discourse.group/t/disaster-with-nexcloud-3-4-0-client/141/1 "2021-12-27T19:06:44Z")
Hi, in the begining of december, Nexcloud update hus client to 3.4.0… but many peopel who update that, get destroyed local time stamp of many of thier files… > **[Desktop client 3.4.0 destroys local time stamp and keeps uploading data to...](https://help.nextcloud.com/t/desktop-client-3-4-0-destroys-local-time-stamp-and-keeps-uploading-data-to-server/128512)** > > The problem is known and lot of users are affected. for details see Desktop Pre Release 3.4.0-rc1 - help test! - #3 by wwe or related Github issues below. @rakekniven please pin a warning to NOT upgrade the client to 3.4.0 (problem might be... It was a disaster, ant they erased that version and taked out a new version 3.4.1, taht yoy can find now… But many people like me, has HUNDRED of files with no date (or 0:00 1/1/1970), an now thos files can not be sincronized… NEXCLOUD has put a solution here: > **[Home](https://github.com/nextcloud/desktop/wiki/)** > > 💻 Desktop sync client for Nextcloud. Contribute to nextcloud/desktop development by creating an account on GitHub. but I am not able to start that solution because I do not know the arguments to put in this order: 1. Call it with the following arguments: `./solvable_files.sh ` for Syncloud / Nextcloud case Some help? ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [28 December 2021 16:38 UTC](https://syncloud.discourse.group/t/disaster-with-nexcloud-3-4-0-client/141/2 "2021-12-28T16:38:13Z")
unfortunately this script is for MySQL database but syncloud uses Postgres database, so it needs some fixing. Is there no other workaround, like re-upload the files again? ---
**Author:** ![janseta](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@janseta](https://syncloud.discourse.group/u/janseta)\ **Post date:** [28 December 2021 17:43 UTC](https://syncloud.discourse.group/t/disaster-with-nexcloud-3-4-0-client/141/3 "2021-12-28T17:43:43Z")
When I installed the 3.4.0 client at the beginning of December with this bug, the time signature of all my files has been destroyed … and then it has synchronized the files without a valid date with those of my computer … with which it also destroyed them … Luckily, I had a recent backup copy, which was not complete but covered 70-80% of these files … So I uninstalled the 3.4.0 client and got the backup back, but it only served me for that 80% of files … and I still have 1-2tb of small files with no valid date … This time, in Nexcloud they have excelled ;-( ---
**Author:** ![janseta](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@janseta](https://syncloud.discourse.group/u/janseta)\ **Post date:** [29 December 2021 11:52 UTC](https://syncloud.discourse.group/t/disaster-with-nexcloud-3-4-0-client/141/4 "2021-12-29T11:52:43Z")
> [@boris](#): > > this script is for MySQL database but syncloud uses Postgres database, so it needs some fixing. I asked them directly… > > > \### :memo: TO DO > - \[x\] :arrow\_up: Bump VERSION.cmake to 3.4.1 and doc/conf.py …(release to 3.4.1) in the corresponding stable branch > - \[x\] :label: Create tag from corresponding stable branch on the commit introducing the version bump > \`\`\` > $ git checkout stable-3.4 > $ git pull > $ git tag -s -m "Release 3.4.1" v3.4.1 > $ git push origin --tags > \`\`\` > \- \[x\] :label: Create tag from corresponding stable branch in client-building. Steps to create the tag are the same as the above. > \- :factory: Trigger the builds on brander and wait for them to succeed: > - \[x\] :penguin: Linux > - \[x\] :apple: Mac OS > - \[x\] :door: Windows MSI > \- :test\_tube: Execute the bugfix release test plan for each build: > - \[x\] :penguin: Linux > - \[x\] :apple: Mac OS > - \[x\] :door: Windows MSI > \- \[x\] :book: Get changelog using \[github\_helper scripts\](https://github.com/nextcloud/github\_helper/), with previous 3.4 release as origin point > \- :book: Create draft pre-release at: > - \[x\] \[nextcloud/desktop/releases\](https://github.com/nextcloud/desktop/releases) with the changelog > - \[x\] \[nextcloud-releases/desktop/releases\](https://github.com/nextcloud-releases/desktop/releases) > \- :package: Upload binaries to: > - \[x\] the draft pre-release at \[nextcloud/desktop/releases\](https://github.com/nextcloud/desktop/releases) > - \[x\] the draft pre-release at \[nextcloud-releases/desktop/releases\](https://github.com/nextcloud-releases/desktop/releases) > - \[x\] download.nextcloud.com in the user home directory (so still private) > \- \[x\] :old\_key: Sign binaries (\`ssh -P 2200\` to signing VM, then, \`cat how-to-sign\`, then \`scp -P 2200\` to download signatures) > \- \[x\] :bellhop\_bell: Notify Marketing that the release is ready > \- :rocket: When marketing gives the go then publish the draft pre-releases created previously at: > - \[x\] \[nextcloud/desktop/releases\](https://github.com/nextcloud/desktop/releases) > - \[x\] \[nextcloud-releases/desktop/releases\](https://github.com/nextcloud-releases/desktop/releases) > - \[x\] run the publish\_desktop.sh script on download.nextcloud.com so that the binaries appear at \[download.nextcloud.com/desktop/releases\](https://download.nextcloud.com/desktop/releases) > \- \[x\] :up: Change the \[updater server\](https://github.com/nextcloud/client\_updater\_server/blob/master/config/config.php) config to serve the release > \- \[x\] :up: Change the \[install-clients\](https://github.com/nextcloud/nextcloud.com/blob/master/strings.php#L6) config to update the link to the latest release on Nextcloud website I will cross the fingers somebody hels me with my 300 Gb of files that now are broken…