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

[Bug]: When adding more than one transaction, the account name doesn't get resest. #2265

New Issue
Open
opened 2026-02-28 20:08:26 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:08:26 -06:00
Owner
Copy Link

Originally created by @RahulShagri on GitHub (Jul 6, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A recent bug fix fixed the notes not being erased after entering a new transaction from the Actual Budget 'New Transaction' Widget app on Android. However, the account name still doesn't get erased. This not only happens when using "New Transaction" widget, but also when entering multiple new transactions using the App itself.

How can we reproduce the issue?

  1. Open Actual Budget on Android
  2. Add a new transaction using the "+" icon at the bottom of the screen
  3. Go back and hit the "+" icon again. The account name that was used in the previous transaction has not reset

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Chrome

Operating System

Mobile Device

Originally created by @RahulShagri on GitHub (Jul 6, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? [A recent bug fix](https://github.com/actualbudget/actual/issues/4794#issuecomment-2847492560) fixed the notes not being erased after entering a new transaction from the Actual Budget 'New Transaction' Widget app on Android. However, the account name still doesn't get erased. This not only happens when using "New Transaction" widget, but also when entering multiple new transactions using the App itself. ### How can we reproduce the issue? 1. Open Actual Budget on Android 2. Add a new transaction using the "+" icon at the bottom of the screen 3. Go back and hit the "+" icon again. The account name that was used in the previous transaction has not reset ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Chrome ### Operating System Mobile Device
GiteaMirror added the user interfaceresponsivebug labels 2026-02-28 20:08:26 -06:00
GiteaMirror commented 2026-02-28 20:08:26 -06:00
Author
Owner
Copy Link

@ShayanAraghi commented on GitHub (Aug 7, 2025):

Hey @matt-fidd @RahulShagri , I took a look at the codebase and it looks like the current behavior where the account name (and date) from the last transaction is prefilled is intentional for the mobile view.

In TransactionEdit.jsc, there's this useEffect block

  useEffect(() => {
    if (isAdding.current) {
      setTransactions(
        makeTemporaryTransactions(
          locationState?.accountId || lastTransaction?.account || null,
          locationState?.categoryId || null,
          lastTransaction?.date,
        ),
      );
    }
  }, [locationState?.accountId, locationState?.categoryId, lastTransaction]);

Here, lastTransaction is pulled from Redux:
const lastTransaction = useSelector(state => state.queries.lastTransaction);

From what I can tell, lastTransaction isn't used anywhere else in this component. Since the user interface says "New Transaction", and the user isn't starting from an account screen, it may be a good idea if the form started completely from a blank state, rather than carrying over the account and date from the last transaction. Happy to hear your thoughts or if there's a UX reason behind keeping it.

@ShayanAraghi commented on GitHub (Aug 7, 2025): Hey @matt-fidd @RahulShagri , I took a look at the codebase and it looks like the current behavior where the account name (and date) from the last transaction is prefilled is intentional for the mobile view. In TransactionEdit.jsc, there's this useEffect block ``` useEffect(() => { if (isAdding.current) { setTransactions( makeTemporaryTransactions( locationState?.accountId || lastTransaction?.account || null, locationState?.categoryId || null, lastTransaction?.date, ), ); } }, [locationState?.accountId, locationState?.categoryId, lastTransaction]); ``` Here, lastTransaction is pulled from Redux: `const lastTransaction = useSelector(state => state.queries.lastTransaction);` From what I can tell, lastTransaction isn't used anywhere else in this component. Since the user interface says "New Transaction", and the user isn't starting from an account screen, it may be a good idea if the form started completely from a blank state, rather than carrying over the account and date from the last transaction. Happy to hear your thoughts or if there's a UX reason behind keeping it.
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 responsive user interface
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#2265
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?