How to migrate from catfriend last or nel0x syncthing-android to syncthingtray android version?

[Adhjie]

I have read both docs about migration on syncthing-android and syncthingtray, but still don't get how to do android version migration from syncthing-android to syncthingtray, is it as simple as importing the .zip file?
I can't risk of data loss, so currently i have migrate from catfriend1 last release to nel0x version. But haven't got enough info on how to safely migrate from syncthing-android to syncthingtray android version.
links:
https://github.com/nel0x/syncthing-android-gplay/blob/main/wiki/migration/Switching-from-the-deprecated-official-version.md

https://github.com/Martchus/syncthingtray/blob/master/docs/android.md#migrating-data-from-your-existing-app-setup

[Martchus]

Current state of the import/migration feature

The import is still buggy in the latest release 2.0.4. Updating Qt lead to some regressions and the import/export using a Zip archive also had some bugs as I haven't tested all cases before. I've already fixed these various details with the commits I've just pushed to the master branch today. Only with that this is expected to work smoothly so I'd wait for the next release or build from master.
EDIT: If anyone wants to help me testing, here's the latest development build of the app for aarch64 devices: https://martchus.dyn.f3l.de/shares/apks

With this it is really as simple as importing a Zip file. You just have to enable this under "Tweaks" as the default import/export method is not using an archive. You'll also have to enter the encryption password if the archive is encrypted. (By default, the import/export feature let's you select a directory for import/export. Maybe I should change the default to use an archive under Android.)

NOT recommended: full database import

If you do a full import with the database, then you have to ensure that the app you exported that database from is stopped and never started again. Otherwise you'll have two different Syncthing devices that claim the same identity but use different databases. That will probably break things. So I do NOT recommend that. (The app will also turn into a red theme like with other potentially dangerous options if you select the full import.)

recommended: import only folder and device settings

If you just import the folder and device settings, then the Syncthing Tray app will simply be another new Syncthing instance (with a different device ID). That new Syncthing instance can be installed alongside any other Syncthing app on the same device (as it will still have a different device ID). This kind of setup doesn't cause any data loss and being able to have multiple apps installed at the same time can be useful for comparing the apps. (You should probably avoid running the two Syncthing instances at the same time, though.) That's also why I recommend only importing folder/device settings. (And that's also how I migrated my own devices. I only uninstalled the Syncthing-Fork app very recently on my devices in response to Catfriend no longer maintaining it. Before that I had both apps installed and also opened the one from Catfriend once in a while.)

To be extra safe, all devices and folders are imported in the "Paused" state so you can review what has been imported (and maybe do changes if needed) before Syncthing will do anything. There will also not happen much besides scanning until you accept sharing the folder on at least one other device.

Of course I still can't give any guarantees regarding data loss.

[Martchus]

I'm not sure what you mean with "syncthing base app version".

I can only say that the Syncthing Tray app will always use its bundled version of Syncthing (which is currently at version 2.0.12) unless you point it to some external executable (which I have never tested under Android). So having different apps installed at the same time leads to different versions of Syncthing itself installed/configured/used that can and will operate independently of each other. They will of course manage the same directories if you configure it like that, e.g. by doing any kind of import. (And they will use the same device ID if you do the non-recommrnded full database import which can lead to breakage as explained before.)

[Adhjie]

Okay, I can't express the word there. So the syncthing app itself is bundled with syncthingtray.

[Martchus]

I'm just not sure what you mean with "syncthing app".

I'm using the following terminology (which should maybe be explained in the documentation):

• "Syncthing" or "Syncthing itself": The Go-based Syncthing service/daemon/CLI you can find on https://github.com/syncthing/syncthing. (I don't think it is a good idea to call it "… app". It is of course a command-line application but calling it "… app" when talking about Android makes it sound like it could be built as an APK file which is not implemented by the build system of "Syncthing" to my knowledge.)
• "Syncthing Tray": This project. At this point it provides various utilities/integrations for "Syncthing". It can be built so that the resulting executable/APK bundles/includes "Syncthing". The builds I provide for Android (and some other platforms) do bundle "Syncthing". "Syncthing Tray" is also the display name of the primary and most generic integration this project provides.
• "Syncthing App": The display name of the the app that is produced when compiling "Syncthing Tray" for Android. I chose this name because "Syncthing App" makes more sense on Android than "Syncthing Tray" and because it is more catchy. I hope this doesn't cause too much confusion.
• "Syncthing Plasmoid": The name of the KDE Plasma applet (or "plasmoid") that is produced when compiling "Syncthing Tray" for GNU/Linux with KDE integrations. Not relevant for Android; I'm just mentioning it here so one might see the pattern.
• "Syncthing-Fork": The app developed by Catfriend which also bundles "Syncthing".

[Adhjie]

I didn't think it about it long enough, so basically web GUI in official desktop Syncthing in windows, catfriend1 or nel0x syncthing-fork GUI wrapper;
web GUI is a GUI that is accessed on web browser, the interface needs web browser;
What does "wrapper" in GUI wrapper mean, is it like android GUI app as an interface for Syncthing CLI?

So the wrapper of catfriend1 is made from java or Kotlin, while your wrapper is made with QT, catfriend1 version has web UI option, while your android version acts as a bundled Syncthing only, while the interface for web UI is accessed from web browser.

With unix socket option enabled, I still could accessed the web UI, but other app can't accessed syncthing web UI, right?

In any case, thanks for the clarification.🙏🏼🙏🏼🙏🏼 Syncthing is made as CLI first, I get it. The GUI comes later.

Sorry for the questions, I think it's better to ask it here than asking it on the forum, I should've researched wrapper vs web UI first, while the main syncthing is of course made with GO. Theres also mobile Golang as in RCX discussion with rsync maintainer in creating the android version of rysnc, but this is out of syncthing scope, since it's just about web UI, wrapper, and syncthing CLI.

Maybe I should ask nel0x for wrapper definition since he's the next catfriend1 syncthing fork maintainer after catfriend1 went AFK.

Edit 1:

BTW, could you elaborate on what does unix socket domain feature does, especially for import export here, or just general usage, if you dont mind?

Let me just C&P the relevant documentation:

It is a good idea to enable authentication for accessing the web-based UI, as otherwise, any other app would be able to access it. A username and password can be configured under “Advanced → Syncthing API and web-based GUI”. Alternatively, you can enable the use of a UNIX domain socket under “Tweaks”. This also prevents other apps from accessing the web-based UI by making it completely inaccessible and, by the way, avoiding communication overhead.

Okay so other apps can't snoop or access syncthing web ui at its URL, which is 127.0.0.1, another IP for local host. But I still could access it from web browser, because syncthing tray android version doesn't have a web UI window inside its app, unlike catfriend1 version. Is this a normal way to access the web UI, or does it fall into the dangerous option of making syncthing web UI accessible remotely?

[Martchus]

syncthing tray android version doesn't have a web UI window inside its app

Yes, I haven't implemented an in-app web view that would somehow inject credentials/auth.

Is this a normal way to access the web UI, or does it fall into the dangerous option of making syncthing web UI accessible remotely?

I recommend enabling auth for the web UI. Otherwise other apps can access it which I would consider dangerous. This is also true if you set the listing address to 127.0.0.1. This is not true when using a Unix domain socket but then the web UI becomes completely inaccessible.

[Martchus]

I've just migrated my old Nokia 7 Plus with Android 10 that I keep as backup phone and it works (using the version from https://martchus.dyn.f3l.de/shares/apks).

I did the following concrete steps:

1. I opened the Syncthing-Fork app and ensured that all directories are up-to-date.
2. I exported an encrypted archive from the Syncthing-Fork app.
3. I closed the Syncthing-Fork app and opened the Syncthing Tray app. I gave necessary permissions and enabled use of a UNIX domain socket.
4. I selected to use an archive for import/export under "Tweaks" and entered the encryption password.
5. I selected the folders and devices I wanted to import and clicked on the "Import" button on the top-right corner.
6. I allowed sharing the folders with this new Syncthing device on other devices.
7. I uninstalled the Syncthing-Fork app.
8. I did an export/backup in the Syncthing Tray app. This also restarted Syncthing and made the change to use a UNIX domain socket effective.
9. I installed "Material Files" on that phone to access the directories from the Syncthing Tray app that are exposed via its "DocumentProvider". (The pre-installed app "Files by Google" unfortunately doesn't allow this.)
10. I installed the app "Crash Log Viewer" to be able to get logs in case the app would crash (which didn't happen so far, though).

These concrete steps worked for me. These steps are of course a bit opinionated, e.g.:

• I could have kept the Syncthing-Fork app installed as I did on my primary phone for a long time. (One should just avoid starting both apps at the same time.)
• Step 9 is of course also completely optional and I only did it to see whether the DocumentProvider works at all.
• Instead of configuring the use of a UNIX domain socket, I could have also set a password for the UI to prevent arbitrary apps from accessing it.

[Adhjie]

Okay, I used the unix domain socket option for now. maybe there needs to be a documentation for people that prefer both configs at browser UI and syncthing tray app, not sure if thats doable or will be synced. so far I'm gonna learn the inside settings of syncthing tray until that option is elaborated.

edit 1:
sorry, forgot to add this as comment, i add this initially as answer.

[Martchus]

It is not easy to understand what your asking exactly. I guess I can't give anymore help regarding this than I've already written down in the documentation.

[Adhjie]

Okay, that's fine. I'm fine with using the UNIX domain socket option. So with this option even without setting up the username and password for GUI in the setting option, the syncthing tray app web UI is closed for any app to connect to?

I check it with the default 127:0.0.1:8384's URL in browser app, and it's not accessible, if that's the case then, I have no more question. after this question is answered then, I'll mark* this discussion as resolved.

[Martchus]

Yes, when using the UNIX domain socket it is completely inaccessible to other apps, including browsers. (That is because the path of the socket is in a directory that's private to the Syncthing App.)

[Adhjie]

I'm gonna discuss this again later, for now I'm just gonna use unix domain socket. When I got the time, I wanted to ask how to get the https certificate for webUI login instead of unix domain socket. Is there other way to mimic the webUI in syncthingtray, or the log file is enough for now?
I do realized syncthing tray is heavy, it is a good app that is based on cross platform QT as a method to create app. Im just gonna force close if its too heavy and I need to clear my phone memory. Much obliged for the app development, I'm sorry 🙏 that I sound a bit narcissistic in the past, but now I understand, it's not easy to put aside free time on making FOSS app.

edit 1:
🙏