github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #6357] [Bug]: Mobile future transaction a schedule prompts when already scheduled #51833

New Issue
Closed
opened 2026-04-30 19:26:48 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-30 19:26:48 -05:00
Owner
Copy Link

Originally created by @shall0pass on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6357

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If you are using the mobile view to post a transaction, if you edit the transaction, it will prompt you to create a schedule for a future dated transaction even if the posted transaction is already linked to a schedule. This can be replicated with a desktop browser using the mobile emulator.

How can we reproduce the issue?

  1. Open app.actualbudget.org
  2. Create the demo budget
  3. Ensure mobile view is activated
  4. Go to the "Bank of America" account
  5. Post the transaction that is "Upcoming". Ensure you use the scheduled date, do not "Post today".
  6. Edit the transaction. (This is where I might update the actual amount information). Changing something is not required.
  7. Save changes.

This transaction is already linked to a schedule. The user should not be prompted to create a new one-off schedule for this.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Mobile Device

Originally created by @shall0pass on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6357 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? If you are using the mobile view to post a transaction, if you edit the transaction, it will prompt you to create a schedule for a future dated transaction even if the posted transaction is already linked to a schedule. This can be replicated with a desktop browser using the mobile emulator. ### How can we reproduce the issue? 1. Open app.actualbudget.org 2. Create the demo budget 3. Ensure mobile view is activated 4. Go to the "Bank of America" account 5. Post the transaction that is "Upcoming". Ensure you use the scheduled date, do not "Post today". 6. Edit the transaction. (This is where I might update the actual amount information). Changing something is not required. 7. Save changes. This transaction is already linked to a schedule. The user should not be prompted to create a new one-off schedule for this. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Mobile Device
GiteaMirror added the transactionsbuggood first issue labels 2026-04-30 19:26:49 -05:00
GiteaMirror commented 2026-04-30 19:26:54 -05:00
Author
Owner
Copy Link

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

@matt-fidd

<!-- gh-comment-id:3638410327 --> @youngcw commented on GitHub (Dec 10, 2025): @matt-fidd
GiteaMirror commented 2026-04-30 19:26:55 -05:00
Author
Owner
Copy Link

@officeboy commented on GitHub (Dec 19, 2025):

This whole update (https://github.com/actualbudget/actual/pull/6065) needs some rethinking and a few different users to chime in.

The original posted reason for the fix makes sense but I enter so many transactions for the next 1-2 days and this button popping up is driving me crazy.

<!-- gh-comment-id:3675671778 --> @officeboy commented on GitHub (Dec 19, 2025): This whole update (https://github.com/actualbudget/actual/pull/6065) needs some rethinking and a few different users to chime in. The original posted reason for the fix makes sense but I enter so many transactions for the next 1-2 days and this button popping up is driving me crazy.
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 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#51833
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?