For those using it on Android, a reminder that the older app is not maintained anymore and you might want to replace it with Catfriend1/syncthing-android.
But also - maybe wait for the app v2.0 to be released to upgrade the desktop client at the same time; I don’t know if using v2.0 on the desktop would work with the v1.x app.
Oh wow, they already have a 2.0 prerelease build. That was fast!
I’m in no rush. 1.x has been doing its job without demanding any of my attention since I set it up a year or so ago. Setup was a bit complex, but it was definitely worth learning.
I’m not sure how fast the pacman repo updates, but I’m using that plus Syncthing-Fork from F-Droid. I don’t think they’ve dropped 2.0 in there, yet.
Looks like the Arch Syncthing package upstream URL is the official Syncthing and is running 2.0.1. I can now confirm that 1.x from Syncthing-Fork works fine with Syncthing 2.0. I just set it up this morning, oddly enough.
I tried it, but it didn’t work for me, so I had to reintroduce the device and share the directories again. But you don’t have to transfer all the data again, it’ll just do a full scan and transfer the diff as usual.
Thanks for the info. I will try upgrading now.
To save people a click, here are the instructions:
On Syncthing on the official app, go into the settings and create a backup.
Confirm you can see that backup in your files.
Now stop the official app entirely using the system app settings for Syncthing (force stop the app basically - we need to ensure it’s not running).
Install Syncthing-Fork v1.29.7.1
Now start Syncthing-Fork.
In the Syncthing-Fork settings, restore the backup you created earlier.
Like magic, everything should be as it was in Syncthing official.
Confirm everything looks good.
Uninstall the official Syncthing app.
Delete the syncthing configuration backup from backups/syncthing.
Upgrade to the latest Syncthing-Fork version
I just tried. Old app exports a directory, new one wants a zip. Zipped the dir and offered to new one. New one complained that some expected file was missing. Gave up and set it up again with it’s new keys (phone only syncs one dir off my home server, not a big deal) and now it’s going great.
I could export and import with minimal issues around half a year ago after it was discontinued.
Based on what @eager_eagle@lemmy.world said maybe try installing an older version, importing, then updating.
For those using it on Android, a reminder that the older app is not maintained anymore and you might want to replace it with Catfriend1/syncthing-android.
But also - maybe wait for the app v2.0 to be released to upgrade the desktop client at the same time; I don’t know if using v2.0 on the desktop would work with the v1.x app.
Oh wow, they already have a 2.0 prerelease build. That was fast!
I’m in no rush. 1.x has been doing its job without demanding any of my attention since I set it up a year or so ago. Setup was a bit complex, but it was definitely worth learning.
Waiting till Material 3 update to use it
I’m not sure how fast the pacman repo updates, but I’m using that plus Syncthing-Fork from F-Droid. I don’t think they’ve dropped 2.0 in there, yet.
Looks like the Arch Syncthing package upstream URL is the official Syncthing and is running 2.0.1. I can now confirm that 1.x from Syncthing-Fork works fine with Syncthing 2.0. I just set it up this morning, oddly enough.
yeah, I decided to try it and it’s working for me too; at least for the usual sync operations
Can I move from the older app to the fork while keeping all my configuration?
I tried it, but it didn’t work for me, so I had to reintroduce the device and share the directories again. But you don’t have to transfer all the data again, it’ll just do a full scan and transfer the diff as usual.
Thanks for the info. I will try upgrading now. To save people a click, here are the instructions:
I just tried. Old app exports a directory, new one wants a zip. Zipped the dir and offered to new one. New one complained that some expected file was missing. Gave up and set it up again with it’s new keys (phone only syncs one dir off my home server, not a big deal) and now it’s going great.
There are instructions on the repo on moving to the fork, you need to download a specific version to do it and then update.
I could export and import with minimal issues around half a year ago after it was discontinued.
Based on what @eager_eagle@lemmy.world said maybe try installing an older version, importing, then updating.
Also tried with the oldest version of the fork on f-droid, it could not import the old app’s config.
The archive repo has the old versions, the main repo omly goes back a few weeks.