Open Busterama452 opened 10 months ago
Yes it's a known limitation
Yes it's a known limitation
I didn't find it in any of the documentation for the application. It's not known to the users paying for this service.
Even though a proper solution to this issue would be nice, for me personally the situation would already be a lot better if the differences could be shown. I'm thinking of something like:
Edited Cloud:
Edited Local:
Edited both (i.e. the real conflicts):
That way I at least know which local POIs to "park" in a separate category, before I overwrite my local copy with the cloud version. I can then manually move these POIs later, and sync again.
Something like this would at least make it possible to manually resolve the situation without loss. And if you choose to lose the data, at least you can do so knowing what you will lose.
Description
If two different devices add different favorites into the same favorites category, osmand cloud can only sync one of those favorites and the other will be lost.
Steps to reproduce
Setup two devices with the same account under OSMAND Cloud.
Create a favorite named "device 1" on mobile device 1 in a category called "sync check". Create a favorite (different location) named "device 2" on mobile device 2 in a category called "sync check". cloud sync device 1 cloud sync device 2
Device 2 will have a conflict in that favorites category "sync check" yet there is no conflict. The favorites are completely different.
Actual result
You have to choose which category to keep, but that loses one of the favorites.
Expected result
Synchronize the favorites so that both favorites exist on both devices.
Your Environment (required)
Device 1 is an OsmAnd Version: Android 4.5.10 Android/iOS version: 11 Device model: Samsung Tablet Tab A 8" Tablet
Device 2 OsmAnd Version: Android 4.5.10 Android/iOS version: Android 8.0.0 Device model: LG Phone VS995