Symptom: loading https://deckdle.neb.host/# after having played the Daily game on a prior day shows that I've already played the day's game, even though I haven't.
Looking at localStorage.deckdle-state-daily, the latest item in that array does update the setupId and timestamps instead ofcreating a new entry. The below screenshot was taken the morning of July 30th, after having cleared the cookie on 7/28, playing, and then completing that day's game, and then a successful loading of the page (and game completion) on the 29th - but on the 30th it thought I'd already played on load. Looking at the screenshot you can see that [0] has a 7/28 date, and [1] has a 7/30 date, there should (I believe) be a [0] for 7/28, [1] for 7/29, and [2] for 7/30.
Workaround: delete localStorage.deckdle-state-daily
Symptom: loading https://deckdle.neb.host/# after having played the Daily game on a prior day shows that I've already played the day's game, even though I haven't.
Looking at
localStorage.deckdle-state-daily, the latest item in that array does update thesetupIdand timestamps instead ofcreating a new entry. The below screenshot was taken the morning of July 30th, after having cleared the cookie on 7/28, playing, and then completing that day's game, and then a successful loading of the page (and game completion) on the 29th - but on the 30th it thought I'd already played on load. Looking at the screenshot you can see that [0] has a 7/28 date, and [1] has a 7/30 date, there should (I believe) be a [0] for 7/28, [1] for 7/29, and [2] for 7/30.Workaround: delete
localStorage.deckdle-state-daily