-
Notifications
You must be signed in to change notification settings - Fork 415
Syncthing stops when switching Android user profile #1953
Comments
Don't know what you mean by "run as a service" on android. Generally yes, there's no support for multiple profiles - the syncthing instances will conflict in various ways. There are no plans of adding support for that, see https://github.com/syncthing/syncthing-android#no-feature-request-taken-feature-contributions-case-by-case |
My apologies. I took it for granted that "run as a service" means the same thing for all computers, regardless of the OS/platform. When I configure something to run as a system service I expect it to start running when the device is powered on, and then to keep running in the background in perpetuity while the device is powered on, regardless of whether any OS-level user accounts are logged in or not. Syncthing for Android appears to offer such a configuration under But it does not work as expected. Hence this bug report. |
Ah yeah, my confusion stemmed from the fact that there's actual different ways to "run" (manage the lifetime of) syncthing on other platforms - while this option "just" makes the app and thus syncthing start automatically. Anyway "run as a service" is perfectly sensible given the name of this options, and I could have recognized that. As for the actual issue: If you can reproduce without using syncthing-android in multiple profiles, please let me know and we can re-open. |
Just to be clear: I am using Syncthing on an Android device that has multiple Android user accounts, but only one of those user accounts (mine) is using Syncthing. I am not trying to have multiple users with separate Syncthing configurations on the same Android device. |
That clarifies things. Logs through |
I have configured Syncthing to run as a service but I often find that it isn't running and I have to start it manually.
I think the issue is that this device is shared by multiple people, and it seems that Syncthing gets shut down when switching user accounts. But if it's running as a service I expect that it should keep running no matter which account is in use.
Version Information
The text was updated successfully, but these errors were encountered: