Well … I can’t reproduce the “zombie” issue, but I’m almost sure it was due to a mix of enabling/disabling/renaming operation (img attached)
It’s possible to have routes with the same name in SA (guess it’s intentional) but this can create some trouble due to the previously identified data problem
0_1534002035882_duplicates.jpg
*** Boring Test ALERT ***
*** Skip the rest of the message if you’re not interested in nerdy debug stuff ***
Starting point : Previous post
Renamed Route A -> Aren
Sync - 9 Routes in watch - Route Aren in watch
Disabled Route Aren - OK (Toggle off)
Sync - 8 Route in watch - Route Aren removed from the watch
Renamed Route B -> Bren
Enabled Route Bren
Sync - 9 Routes in watch - Route Bren in watch
Enabled Route Aren - OK (Toggle on)
Sync - 9 Routes in watch - Route Aren in watch, Route Bren disappeared
Renamed Route Aren -> Aren2
Sync - 9 Routes in watch - Route Aren2 in watch
Disabled Route Bren - OK (Toggle off)
Sync - 8 Route in watch - Route Aren removed from the watch
Enabled Bren - OK
Renamed Bren -> A
Sync - 8 Route in watch - Error in App “! Failed to add route to watch” (Toggle off)
Renamed Aren2 -> A
Sync - 8 Route in watch - But in SA Route A (Toggle on)
Enabled Route A (the one was Bren) - OK
Sync - 9 Routes in watch - Route A (the one was Bren) in watch but now it’s not possible to know which one from SA was sent as both toggle are on and data are messed up 🙂
“cleaned” the SA routes
Disabled Route A (the one was Bren) - OK (Toggle off)
Sync - 8 Route in watch
Disabled Route A - OK (Toggle off)
Sync - 8 Route in watch - Error in App “! Failed to add route to watch” (Toggle off)
Deleted all SA routes
Sync - 8 Routes in watch
Sync via Suuntolink
… now it’s time to move 😁