Update to 2.18.20 failing twice

[Dimitrios Kanellopoulos]

@soylent-yellow please send logs

[zadow]

@soylent-yellow I am with you, I experienced the same problem

[zadow]

@dimitrios-kanellopoulos does it make sense to send logs, when I already (soft) restarted watch twice? and also I discharged it to zero and charged it back to 100% , so any error related logs from watch are most likely gone, right?

[Bulkan]

@zadow as far as I know they need the logs to work on it. Please send it.

[isazi]

@zadow if this happened more than 24h ago, it’s gone.

[zadow]

@isazi , hm, thanks, then, it’s gone…

[isazi]

@zadow best thing to do is to send logs immediately after something weird (like this) happens, and send the log ID to Dimitrios.

[Soylent Yellow]

@isazi OK, them I’m too late too. I read the replies just now (Wednesday) and the reset happened last Sunday. Well, I’ll make sure to send logs directly next time anything weird happens.

[Soylent Yellow]

@dimitrios-kanellopoulos I just sent the logs with log ID 59018271684968

There seems to be discussion here that logs need to be less than 24 hours old to be of any help, but when I look at the file

~/Library/SuuntoLink/suuntolink_ui.log

then I see that its still contains all events from 2021-10-03 (last Sunday).

Or is the data needed from other log files as well? I can probably still retrieve the state of the whole Suuntlo library from log files if necessary/

[Dimitrios Kanellopoulos]

@soylent-yellow said in Update to 2.18.20 failing twice:

59018271684968

you can also zip those and pm me with a drive lin k