There’s a known bug, which manifests in conflicts if you have an android phone. A fix is already release to android gplay beta, and the main release is pending google’s review (approx 1d). You could disconnect your android device until the release is out.
Only another additional @imsodin , I’ve just noticed there was an update for the android device. I have updated and tested and all seems well.
As an active user that has started depending on ST, has there ever been an issue with a ST install that has led to catastrophic failure of a file structure, or are there precautions against that happening? I only ask, before I start recommending and assisting others with the use of ST.
It is of course great work that all contributors do and I’m not trying to dismiss their effort
This conflict thing has been the most intrusive thing I can remember in the recent past. Generally data safety is our number one concerns (see project goals), so we do take that very seriously. In this case too no data was lost, just a mess created with conflicts (I acknowledge it’s still annoying and potentially disruptive if it happens to a lot of data).
@imsodin thank you! The 1.21.1.1 update seems to have fixed the issue for me too. File changes on Linux that get synced to Android are no longer generating conflict files.
One other data point in case it’s relevant: I installed the 1.21.1.1 update on a current phone running Android 13, which immediately fixed the problem.
I also have an older Android 8 phone that syncs the same folders. That phone is still running 1.21.1 (I didn’t update it) and it is not generating sync conflicts.
