Training session erroneously reported to be a long time ago
l
lennarts
I was reminded by the app now 2 times that my last workout session was a long time ago (first time it said 3 weeks, now it said 5 days ago), and if I wanted to start another session.
However, my last workout was yesterday and I'm still sore! It's not a big bother, but haven't seen such a bug report yet, so here it is :)
Louis Deveseleer
Hm yes that's weird. Do you use several devices for Calistree, or just one phone? EDIT: I checked your public profile, and your last visible session was done 3 weeks ago (January 9). Is your more recent session private?
l
lennarts
Louis Deveseleer
I have only this one device. I think my sessions are shared with buddies only generally, at least the ones from this and last week were.
And correction: I had sessions on Jan 27, Jan 30, Jan 31, and the last one yesterday (Feb 3) before the bug appeared again. I cannot recall the situation when it first appeared.
Thank you for checking! If I can help somehow by providing more info, I'm happy to do so :)
Louis Deveseleer
lennarts To be honest with you, right now I have no idea what could be causing this bug, and this is the only report of that issue that we've received so far, so I think I'll wait to see if other people are affected before looking deeper into it. Please let me know in this thread if it happens again though.
l
lennarts
Louis Deveseleer thanks for looking into it, i completely understand! will keep you updated if it happens again. might be something on my phone specifically.
r
rikbruil
Louis Deveseleer Just want to chime in that I’m also affected by this. I regularly get notifications to schedule something again since it’s been over 90 days since my last training.
The weird thing is that I’ve been training for around one year almost daily, so I wonder if this notification is triggered by some routine I’m no longer scheduling.
Like the above user I believe my sessions are also only visible to buddies.
Louis Deveseleer
rikbruil lennarts Can you please let me know if this still happens after updating to the latest version (5.6) ?