actualbudget/actual

[Bug]: Splitting existing transaction causes UI glitches as splits disappear and reappear

Open

#5217 opened on Jun 21, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (7,129 stars) (603 forks)batch import
buggood first issuehelp wanteduser interface

Description

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I'm not sure how to best summarize the issue, so excuse the awkward title. Splitting an existing transaction seems to cause some kind of synchronization weirdness and makes the UI glitch, as the split transactions disappear and reappear.

Once I'm done splitting the transactions, I'm also left with a 0.00 split transaction.

https://github.com/user-attachments/assets/32325703-1880-40bf-b5f0-d06a3058371d

Just for clarity, in the video I press enter after entering the amount and then I don't press or click anything at all (until you see my start typing again).

None of this happens when creating a new transaction as a split transaction straight away.

How can we reproduce the issue?

I've been able to reproduce this on the demo instance, but it's not as pronounced there, likely because the demo instance has much fewer transactions.

  1. Create a transaction as a non-split transaction
  2. Edit the transaction category to turn the transaction into a split transaction
  3. Enter the first split amount, press Enter
  4. Observe glitchy UI behavior

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Contributor guide

Tech stack
javascriptreact
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the transaction splitting logic in the frontend components. Look into the state management for split transactions, particularly how the UI updates when a non split transaction is converted to a split transaction. Check for any race conditions or missing state updates when pressing Enter after entering the split amount. The video shows splits disappearing and reappearing, suggesting a synchronization issue. Review related GitHub comments for any additional clues.