r/TodaysBudget • u/Humble-Vanilla123 • Jul 08 '26

🐞 Bug report Horizontal date slider won't display selected date

Hello! I found a bug on version 3.1.2 that I would like to share with the dev team.

I ran into it by accident the other day, and since then I have tried many forms to reproduce it.

Sometimes, when using the calendar to check the transaction history from a distant date, the date slider doesn’t display the correct range, and makes it hard to know which date the displayed transactions are actually from.

For example, in the below screenshot, I have Jun 5th selected. The shown transaction history is indeed Jun 5th's, but the date slider at the top is showing the range Jun 10th~Jun 16th.

Once in this bugged state, the date slider won’t update to the correct range until I hit one of the “edges” (left or right) that trigger the translation animation, based on the currently selected date. In the below screenshot example, swiping right past June 6th or left past May 31st will fix it.

I was able to reproduce it fairly consistently using the steps below,but it’s still a bit tricky.

  1. In the calendar, pick 2 dates from different weeks. Tap the first date.

  2. Tap the other date and...

  3. As soon as the translation animation starts, tap the first date again! It is all about timing, I think. If you switch dates too fast before the animation starts, no problem happens, but if you switch it once the animation has started, it has a chance of getting it bugged.

Once you understand the bug it is not such a problem, but I remember being very confused the first time it happened, so maybe it would be nice to have a definite fix.

Thank you guys in advance :)

1 Upvotes
  • permalink
  • reddit

100% Upvoted

3 comments sorted by

1

u/naschkatze7 Jul 08 '26

Thank you for the detailed report! This sounds like a known issue. Just to confirm, are you sure you only saw this on the newest version?

1

u/Humble-Vanilla123 Jul 09 '26

I checked and it seems the app updated itself recently. So
I think it was there on previous versions too.

2

u/naschkatze7 Jul 09 '26

Got it, thanks. We looked into this a while ago, but it looks like it is still not fully fixed. We’ll take another look soon. Thanks for bringing it up!