The weird way logs are handled
-
Hey Guys,
I wanted to make some feedback on the “send logs to Suunto function” as it seems that many of us used it recently, and I think most would concur about how unintuitive it is, here is a few things, question, remarks and advice :
-
Log content :
- most app that allows to send log also usually give a way for the user to see what is being sent, it gives peace of mind regarding personal data, and also helps to see if the relevant trouble is actually part of the log.
-
last sync, log date :
- currently it seems that the logs from the watch are sent…from the last watch sync ? how much (day/hours ?) historic data is sent ?
- do we need to sync the watch first before sending the logs ? or is it done in background ? maybe the best would be to indicate the watch syncing before sending the logs
-
Comments :
- that one is the weirdest, we can send logs, but we can’t say why we’re sending those logs, the only way it seems is to send a message to a developer via this forum or start a chat so that support can make a ticket, this is reaaaalllly sub-optimal
- the best would be to have a small comment window open where we can add the reason we sent logs, and detail stuff like at what precise time the bug occurred, any external factors/remarks
So yeah, my two cents for a future SuuntoApp update
cheers !
-
-
@Elipsus The funny thing is that when I provide feedback on the Suunto App (iOS beta), I can add screenshots and write what I observed. Maybe this functionality is part of https://apps.apple.com/de/app/testflight/id899247664 and not the Suunto App, but what you want is demonstrated in TestFlight/Suunto beta on iOS.