@Christian-Perrier said in 6.5.X:
Hello,
For the record, I went on a very annoying bug yesterday with 6.5.7. Indeed, as I am a Suunto watch user for ages, I didn’t even remember that I was using the beta versions of the app…:-)
So, well, yesterday, after about 10 days without any activity to sync on my watch, I completed one and, as usual, went to the app to get the activity synced. But then a strange behaviour happened : instead of the usual message about syncing “Activity 1/1”, the app screen blinked briefly and then the sync appeared completed. Any further sync attemps then lead to a very quick blink and completion message (with the usual check mark).
After various attempts, I finally deleted the relevant activity on my watch and quickly completed a fake one --> same result. Deleting all old activities in the watch log lead to the same result : any new activity was failing t sync.
Remember that I was indeed not even remembering that I was using the beta version of the app. I don’t even remember when I joined the beta program…:-). I ended trying many various things to solve the problem, even completely deleting the app data on my phone, reinstalling the app and even…completely deleting my account (which I don’t really use as is : all my activities record is kept on Strava). And that includes also fully resetting my watch (hard reset to factory settings!). The main reason to all this is because I have a major race today and I really don’t want to have a 25h activity which I can’t get back on my computer…:-)
But, even with resetting everything the problem was here. I ended up sending my watch journal to the Suunto servers (with SuuntoLink) under the 130284269846000 ID along with a message (in French) to support@suunto.com. Remember that I wasn’t remembering being part of the beta program so I acted just like a random user…:-)
The final solution was found when I finally tried the “what if this is due to a recent update to the app on my phone” solution…:-). There I discovered that the app had been update to 6.5.7 3 days before (Dec. 3rd then) and the first mention that this is a beta version. So I went to the ultimate solution : go back and reinstall an old version. Not being even aware that the beta program probably has specific methods to revert updates, I finally went on APKMirror and found that the last version there is 6.4.7…which I downloaded and installed.
And then everything was working as expected.
So, well, I later read a bit more about the beta program, which lead me to this forum…and then I decided that this problem is important enough for me to send a detailed report of what happened in hope this might help developers or other users.
I ll transfer thisk to the devs