Re: Waypoint note lost during Explore sync on iOS
Posted: Mon Mar 24, 2025 3:59 am
Yes the app is the latest as of today.
Garmin support got back to me, and I've sent them the diagnostics logs from the App, as well as the Garmin folder of the device (sent using Garmin Express). Let's hope they are able to track it down.
From the App logs, I am able to find some relevant entries because of the text I used in the notes (kaboon).
To me this indicates it sent the payload to the device, and received ACK? from the device?
There's more entries in the log that matches the waypoint uuid. But not able to make out why the bug.
Looks like the note part have a timestamp being sent back/forth (epoch down to seconds), so should work assuming it's tracking who made what change and when. The timestamp of the original note from Device edit to phone is 1742778904, which is earlier than 1742778961. So that part is ok.
Anyway hope they can track this down. The reason this is important is because editing the title/notes of a waypoint on the phone is a frequent use case, since editing it on the device is so painfully slow.
Garmin support got back to me, and I've sent them the diagnostics logs from the App, as well as the Garmin folder of the device (sent using Garmin Express). Let's hope they are able to track it down.
From the App logs, I am able to find some relevant entries because of the text I used in the notes (kaboon).
Code: Select all
smart-2025-03-23 17_42.log:589:2025-03-23 18:16:33:486 [com.garmin.exploresync][Device] [3492217748][Debug] smart - onSendResponse: {"status":"READ_STATUS_SUCCESS","waypoints":[{"uuid":"lAMn0AAAAIAAEAAAGwAAAA==","notePart":{"versionStamp":{"editTime":1742778961,"derived":false},"text":"Phone-text-kaboon"}}]}
smart-2025-03-23 17_42.log:598:2025-03-23 18:16:34:654 [com.garmin.exploresync][Device] [3492217748][Debug] smart - onReceivedRequest: {"waypoints":[{"uuid":"lAMn0AAAAIAAEAAAGwAAAA==","dataPartVersionStamp":{"editTime":1742778961,"derived":true},"notePartVersionStamp":{"editTime":1742778961}}]}
There's more entries in the log that matches the waypoint uuid. But not able to make out why the bug.
Looks like the note part have a timestamp being sent back/forth (epoch down to seconds), so should work assuming it's tracking who made what change and when. The timestamp of the original note from Device edit to phone is 1742778904, which is earlier than 1742778961. So that part is ok.
Anyway hope they can track this down. The reason this is important is because editing the title/notes of a waypoint on the phone is a frequent use case, since editing it on the device is so painfully slow.