How can I export the settings of Syncthing (v1.28.0) on macOS (v11.7.10)? I want to revert to using Syncthing 1.27.x because I’m encountering some issues.
(Details of the issue are in the following link)
Or do I have to completely manually rebuild all the settings?
I checked the address Syncthing Configuration — Syncthing documentation, but I couldn’t find the configuration file on my computer. I looked in $XDG_STATE_HOME/syncthing, $HOME/.local/state/syncthing, and $HOME/Library/Application Support/Syncthing, but I didn’t see any files related to Syncthing. I am not using the macOS application package (dmg) to install Syncthing; instead, I used the basic Syncthing release from Releases · syncthing/syncthing · GitHub. I extracted it to a directory, configured the environment variables, and then started it directly in the terminal command line interface using the syncthing command. Unfortunately, I still couldn’t find the related configuration files using find. It’s quite strange because in the directory where I extracted and ran it, there are only executable files named syncthing, along with other files like syncthing.old, .metadata, AUTHORS.txt, LICENSE.txt, README.txt, etc, but no configuration files. This is quite strange.
There’s no need to export any settings, you can just download and run an older version. Set STNOUPGRADE=1 in the environment to prevent automatic upgrades when it first starts. Configuration on macOS is in ~/Library/Application Support/Syncthing, guaranteed.
Oh yes, thank you, I was getting dizzy from all this. The configuration files are indeed in ~/Library/Application Support/Syncthing. I overlooked ‘Application Support’ and that’s why I couldn’t find them (“It’s also my fault for forgetting to use the -iname option with the find command earlier.”). I’ll immediately try using the downgraded Syncthing version v1.27.12 on macOS (which is also the version on my Android phones) to see if it restores normal bidirectional syncing.
Confirmed, on my devices (macOS and Android phones), with the versions macOS-v1.28.0 and Android phones-v1.27.12, the bug mentioned in the issue occurs. When I downgraded the macOS version to 1.27.12, everything worked fine. Thank you for your assistance.