But now {tray icon (red)} -> open wouldn’t open the in-browser settings pane. No luck rebooting.
So I remove the app, rm -rf /Applications/Syncthing.app ~/Library/Application\ Support/Syncthing
Now I try
brew cask fetch syncthing
sudo open ~/Library/Caches/Homebrew/downloads/7ec71af62abb4c691f4e27be32cf5f1511c9372ce98d5a542b7a5236a7727c9d--Syncthing-1.0.0-2.dmg
… and drag-drop the .app in to /Applications.
Now it works.
Now {tray icon (green)} -> opendoes open the in-browser settings pane.
I follow the same procedure to install it on my MacBookAir. I allow the update on both machines. I even successfully share a couple of folders with my MacBookAir.
The next day though, something’s not right: https://ibin.co/5L6k0hIJf6SS.png
i.e. it says it is Running (offline). Yesterday the light was green. Today it is yellow. And there is a (!) badge over the trayicon.
It does still seem to be sharing files; I dropped one in to the MacBookAir and pulled it off the MacBookPro.
For the wrapper you should click the menubar icon -> Preferences -> Click the test button to check if the API is working. Or else you need to copy the API key from the web interface Actions -> Settings -> API key.
Brilliant! My API keys were inconsistent.
Now I’ve now got the green light!
I wonder what went wrong. Could it have been the fact that I previously installed/removed SyncThing?
Also, could the software itself enforce consistency between API-key in WebGUI-Settings and in the Prefs menu-item? This looks like a Gotcha that could catch a lot of people, and it is strange for software to have 2 API-key locations…
If not, maybe a doc-note in README.md could shake them loose?