github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: enabling mobile running balance requires going out of and back into the account #2714

New Issue
Closed
opened 2026-02-28 20:25:22 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 20:25:22 -06:00
Owner
Copy Link

Originally created by @db-src on GitHub (Dec 11, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Clicking the account name and then ... button and then "Show running balance" in mobile mode does not update the view to actually show the running balances against the already visible transactions. I have to navigate to a different page (e.g. back to account list) and back into the account's txns to see the balances - which should not be necessary and makes the feature seem like it doesn't work / does nothing!

How can we reproduce the issue?

Open account page / transaction list on mobile and click through acct name, to enable run bal.

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Chrome

Operating System

Mobile Device

Originally created by @db-src on GitHub (Dec 11, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Clicking the account name and then ... button and then "Show running balance" in mobile mode does not update the view to actually show the running balances against the already visible transactions. I have to navigate to a different page (e.g. back to account list) and back into the account's txns to see the balances - which should not be necessary and makes the feature seem like it doesn't work / does nothing! ### How can we reproduce the issue? Open account page / transaction list on mobile and click through acct name, to enable run bal. ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Chrome ### Operating System Mobile Device
GiteaMirror added the transactionsgood first issueresponsivebug labels 2026-02-28 20:25:22 -06:00
GiteaMirror commented 2026-02-28 20:25:24 -06:00
Author
Owner
Copy Link

@db-src commented on GitHub (Dec 11, 2025):

Once the running balance has been shown before, then clicking to toggle Hide/Show do work instantly and not require reloading the page. So this may only be an issue with the very first enablement for a given account.

@db-src commented on GitHub (Dec 11, 2025): Once the running balance has been shown before, then clicking to toggle Hide/Show _do_ work instantly and not require reloading the page. So this may only be an issue with the very first enablement for a given account.
GiteaMirror commented 2026-02-28 20:25:26 -06:00
Author
Owner
Copy Link

@mustafamagdy commented on GitHub (Dec 17, 2025):

Getting issue details and comments

@mustafamagdy commented on GitHub (Dec 17, 2025): Getting issue details and comments
GiteaMirror commented 2026-02-28 20:25:26 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 17, 2025):

Fixed by #6379

@youngcw commented on GitHub (Dec 17, 2025): Fixed by #6379
GiteaMirror commented 2026-02-28 20:25:26 -06:00
Author
Owner
Copy Link

@mustafamagdy commented on GitHub (Dec 17, 2025):

Hi @db-src! I've identified and fixed this issue. The problem was in the desktop component's handling of the running balance toggle - it was clearing all transactions and then refetching them, which caused the empty screen issue on mobile.

I've created PR #6434 with the fix. The solution preserves the existing transactions and just recalculates the running balances, so users will see the balances appear immediately without the empty screen.

Testing the fix:

  1. Open an account on mobile view
  2. Click the account menu (three dots) and select "Show running balance"
  3. Transactions should remain visible and running balances should appear immediately
  4. No more need to navigate away and back!

The fix is minimal and focused - it just removes the problematic code that was clearing transactions and instead uses the existing data recalculation approach that the mobile components already use successfully.

Thanks for reporting this issue!

@mustafamagdy commented on GitHub (Dec 17, 2025): Hi @db-src! I've identified and fixed this issue. The problem was in the desktop component's handling of the running balance toggle - it was clearing all transactions and then refetching them, which caused the empty screen issue on mobile. I've created PR #6434 with the fix. The solution preserves the existing transactions and just recalculates the running balances, so users will see the balances appear immediately without the empty screen. **Testing the fix:** 1. Open an account on mobile view 2. Click the account menu (three dots) and select "Show running balance" 3. Transactions should remain visible and running balances should appear immediately 4. No more need to navigate away and back! The fix is minimal and focused - it just removes the problematic code that was clearing transactions and instead uses the existing data recalculation approach that the mobile components already use successfully. Thanks for reporting this issue!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug good first issue responsive transactions
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2714
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?