@JamieCasper It’s a confirmed bug introduced in the release in February. Unfortunately it has not been resolved yet. Still present in version 6.12.6 released August 5th. The work around is to save with different time value. And then edit the new saved post and change the time value.

@2b2bff You are probably right. The phenomenon exists on both types of operating systems. There is a discussion on the subject in the link that @petrmisek attached.

@Squirrel I came here to comment the same! I second your point but would also add that I miss the previous dark map that allowed multiple activities like multi days treks to glow in the dark! Edit: just realised that the minimal in dark mode does the trick (I am back to light mode)

Hello. I just did a 100mile. 29h, HR strap, light, vibration, notification on, absolutely no problem there. Then I synced to App. Activity shows 161km, which is according to my readings. However, the map doesn’t show the last 1.5 km (approximately) although start and finish where at the exact same location. Also in the app it takes a very long time to load the data, i.e. map, statistics, HR data etc. Anyone has same experience?

@2b2bff It strikes me as absurd that a watch messaging app can’t access the data stored on the watch

It seems to be resolved.

Thanks, reported

@SergioB me too. Nothing. I have the Race Titanium. All Training guides, not in watch even that they appear.

@DefaultUser the alarm did not show on mine when I woke up, but now is working as expected. And I can see tomorrows alarm time again. Sorry missed you were on Race S. I’m on V2.

@Dimitrios-Kanellopoulos https://maps.suunto.com/move/micheleolivieri80/6a5364be8c073465ceefc4d6 The data are correct, buy the app show It correct only the First time, from the second view in the same app session the data are shown without the last number

@surfboomerang missed that! gave yours a rec

@MdzOtt thanks, i’ll give it another try!

@Mitch9 before this last beta update, wathsapp notifications on the watch were preceded by the word “WhatsApp” before the name of the sender of the message (as described few post above). This resulted in being impossible to read the name of the sender of the message. Now with 6.11.8 the problem is solved (at least for me)

@Wilson75 It finally works

@SergioB top I had that issue as well. Reported it anyways

Just got a new update this morning: 6.11.8 and it seems the issue got fixed! The routes are whole after transfer. Thank you Suunto!