[GH-ISSUE #7663] [Bug]: Upcoming transactions discrepancy between web and mobile views #72890

Closed
opened 2026-05-16 13:48:41 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @pogman-code on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7663

What happened?

This is a tricky one, I have a bunch of schedules set for the 1st of the month (~20 spread over multiple accounts). They are all set to create transaction automatically.

For most of them, I have edited their rules to set notes, category and change date (see https://github.com/actualbudget/actual/issues/7662).

The issue I am facing is that on the web view, upcoming transactions appear as expected but on the mobile view only a handful do.

A picture is worth a thousand words:

Image Image

How can we reproduce the issue?

Honestly I don't know how to reproduce the issue, I tried on the test instance to no avail.
I check the console in the web inspector, no specific error either...

I am available to check things if need be, let me know

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @pogman-code on GitHub (Apr 29, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7663 ### What happened? This is a tricky one, I have a bunch of schedules set for the 1st of the month (~20 spread over multiple accounts). They are all set to create transaction automatically. For most of them, I have edited their rules to set notes, category and change date (see https://github.com/actualbudget/actual/issues/7662). The issue I am facing is that on the web view, upcoming transactions appear as expected but on the mobile view only a handful do. A picture is worth a thousand words: <img width="1153" height="368" alt="Image" src="https://github.com/user-attachments/assets/2ded342b-23b0-4f70-949b-a605307f7edb" /> <img width="397" height="314" alt="Image" src="https://github.com/user-attachments/assets/fa4d07bc-666a-46b8-bdb9-05fe268d44bb" /> ### How can we reproduce the issue? Honestly I don't know how to reproduce the issue, I tried on the test instance to no avail. I check the console in the web inspector, no specific error either... I am available to check things if need be, let me know ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the transactionsuser interfacebug labels 2026-05-16 13:48:42 -05:00
Author
Owner

@matt-fidd commented on GitHub (May 3, 2026):

I don't seem to be able to reproduce this either, it's going to be really hard to fix without a repro file. I'll leave this open for now to see if anyone else is hitting a similar bug

<!-- gh-comment-id:4367259896 --> @matt-fidd commented on GitHub (May 3, 2026): I don't seem to be able to reproduce this either, it's going to be really hard to fix without a repro file. I'll leave this open for now to see if anyone else is hitting a similar bug
Author
Owner

@pogman-code commented on GitHub (May 3, 2026):

I just found how to replicate using the demo budget:

  1. Create 3 schedules on the same account named respectively A, B and C set for tomorrow.
  2. Edit schedule B rule, add "set date" action to a later date (late in the month)
  3. Check desktop view, all schedules are visible (including A, B and C)
  4. Switch to mobile view, KO, some schedule are there some not
<!-- gh-comment-id:4367306164 --> @pogman-code commented on GitHub (May 3, 2026): I just found how to replicate using the demo budget: 1. Create 3 schedules on the same account named respectively A, B and C set for tomorrow. 2. Edit schedule B rule, add "set date" action to a later date (late in the month) 3. Check desktop view, all schedules are visible (including A, B and C) 4. Switch to mobile view, KO, some schedule are there some not
Author
Owner

@matt-fidd commented on GitHub (May 3, 2026):

I just found how to replicate using the demo budget:

  1. Create 3 schedules on the same account named respectively A, B and C set for tomorrow.
  2. Edit schedule B rule, add "set date" action to a later date (late in the month)
  3. Check desktop view, all schedules are visible (including A, B and C)
  4. Switch to mobile view, KO, some schedule are there some not

Amazing thank you, I managed to reproduce. I think I've found the fix, can you try this PR https://github.com/actualbudget/actual/pull/7691? (https://deploy-preview-7691.demo.actualbudget.org/)

<!-- gh-comment-id:4367315765 --> @matt-fidd commented on GitHub (May 3, 2026): > I just found how to replicate using the demo budget: > > 1. Create 3 schedules on the same account named respectively A, B and C set for tomorrow. > 2. Edit schedule B rule, add "set date" action to a later date (late in the month) > 3. Check desktop view, all schedules are visible (including A, B and C) > 4. Switch to mobile view, KO, some schedule are there some not Amazing thank you, I managed to reproduce. I think I've found the fix, can you try this PR https://github.com/actualbudget/actual/pull/7691? (https://deploy-preview-7691.demo.actualbudget.org/)
Author
Owner

@pogman-code commented on GitHub (May 3, 2026):

That was fast! Looks like it fixed the issue indeed. And since you sort by date, I guess it fixes #7662 as well ;)

<!-- gh-comment-id:4367324955 --> @pogman-code commented on GitHub (May 3, 2026): That was fast! Looks like it fixed the issue indeed. And since you sort by date, I guess it fixes #7662 as well ;)
Author
Owner

@matt-fidd commented on GitHub (May 3, 2026):

That was fast! Looks like it fixed the issue indeed. And since you sort by date, I guess it fixes #7662 as well ;)

Looks like it! The root cause was the same but the mobile view was confused when it got two sections with the same date on.

<!-- gh-comment-id:4367327123 --> @matt-fidd commented on GitHub (May 3, 2026): > That was fast! Looks like it fixed the issue indeed. And since you sort by date, I guess it fixes [#7662](https://github.com/actualbudget/actual/issues/7662) as well ;) Looks like it! The root cause was the same but the mobile view was confused when it got two sections with the same date on.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#72890