[BUG] Disappearing Diary Entries
Running the latest beta build - 3.19.0 (1265).
I’m not exactly sure what the specific scenario is that causes this, but I will sometimes enter items in my diary group and it will show up and then if I refresh the day, or close and reopen the app, those entries will be gone.
It seems to only happen when my macro targets are near completion for the day ¯\_(ツ)_/¯
I’ve recorded a screencast of the issue, but the forum won’t let me upload it… here’s a link to the file on my iCloud https://share.icloud.com/photos/00bFKu0S1ausaXa1uM4eWdDlg
Comments
-
Thanks so much for reporting this @wdavidow the extra tidbit about it happening only when you are near completing your targets is a new lead! We have had a few reports prior but not much to go on in investigating this yet! Thanks so much for the screen recording as well!
Hilary
cronometer.com
As always, any and all postings here are covered by our T&Cs:
https://forums.cronometer.com/discussion/27/governing-terms-and-disclaimer -
Saw similar things, where it's added to other diary groups or even to the day before instead.
-
A little more detail here: I just went back and looked at the diary entry that I copied over from a previous day and saw a bunch of repeat entries there… is it possible that entries copied from a previous day are somehow causing this issue?
-
copying the entry from a previous day is definitely related… I just tested it, then added a new item and refreshed and it disappeared.
-
yes! It sounds like its related to the recents list in the food search. We should have a new build coming to you soon (Hopefully today) with a fix!
Hilary
cronometer.com
As always, any and all postings here are covered by our T&Cs:
https://forums.cronometer.com/discussion/27/governing-terms-and-disclaimer -
It should be available now @wdavidow
Hilary
cronometer.com
As always, any and all postings here are covered by our T&Cs:
https://forums.cronometer.com/discussion/27/governing-terms-and-disclaimer -
-
Thanks, @Hilary - I just tried the same set of actions I used this morning to reproduce the issue and it didn’t happen… Looks like the issue has been resolved!
