github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2203] [Bug]: PWA - Date of a new transaction can't be different than today's date #15103

New Issue
Closed
opened 2026-04-14 17:57:50 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-14 17:57:50 -05:00
Owner
Copy Link

Originally created by @pascalxricher on GitHub (Jan 9, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2203

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I updated to new latest version and tried to add a new transaction using the PWA.

Regardless of the date I set, the date of the day is persisted.

If I update the transaction using the PWA, the date of the day is always persisted.

If I switch to the desktop version, I can update the date to a date different of today's date.

This seems to be a regression with the previous version.

What error did you receive?

The wrong value is saved.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Mobile Device

Originally created by @pascalxricher on GitHub (Jan 9, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2203 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? I updated to new latest version and tried to add a new transaction using the PWA. Regardless of the date I set, the date of the day is persisted. If I update the transaction using the PWA, the date of the day is always persisted. If I switch to the desktop version, I can update the date to a date different of today's date. This seems to be a regression with the previous version. ### What error did you receive? The wrong value is saved. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Mobile Device
GiteaMirror added the bug label 2026-04-14 17:57:50 -05:00
GiteaMirror commented 2026-04-14 17:57:51 -05:00
Author
Owner
Copy Link

@HansiWursti commented on GitHub (Jan 9, 2024):

Hi,

wanted to report a similiar / same bug.

The new Date field in the split mobile transaction does not update the value if you edit the date and directly click save.

If you edit the date and then "exit" the edit mode by clicking in a blank space and then the transaction date gets updated at least for me.

It seems that the OnUpdate of the Date Field is not fired if directly clicking save.

Maybe it needs to be checked if the date field is in edit mode and process a possible change before saving the transaction.

So probably #2068 @joel-jeremy ?!

Thank you!

<!-- gh-comment-id:1883579081 --> @HansiWursti commented on GitHub (Jan 9, 2024): Hi, wanted to report a similiar / same bug. The new Date field in the split mobile transaction does not update the value if you edit the date and directly click save. If you edit the date and then "exit" the edit mode by clicking in a blank space and then the transaction date gets updated at least for me. It seems that the OnUpdate of the Date Field is not fired if directly clicking save. Maybe it needs to be checked if the date field is in edit mode and process a possible change before saving the transaction. So probably #2068 @joel-jeremy ?! Thank you!
GiteaMirror commented 2026-04-14 17:57:51 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Jan 9, 2024):

At the moment I am struggling to reproduce this. I have added four test transactions. Some in Safari and some on Chrome, all in mobile mode (PWA) on iOS17.

I filled out the amount, payee, category and account. I then clicked date and altered it to 6 January - then Add Transaction. All transactions got added correctly on 6 January.

I am mentioning this in case for some reason it is Mobile OS specific?

<!-- gh-comment-id:1883605546 --> @Kidglove57 commented on GitHub (Jan 9, 2024): At the moment I am struggling to reproduce this. I have added four test transactions. Some in Safari and some on Chrome, all in mobile mode (PWA) on iOS17. I filled out the amount, payee, category and account. I then clicked date and altered it to 6 January - then Add Transaction. All transactions got added correctly on 6 January. I am mentioning this in case for some reason it is Mobile OS specific?
GiteaMirror commented 2026-04-14 17:57:51 -05:00
Author
Owner
Copy Link

@HansiWursti commented on GitHub (Jan 9, 2024):

I can replicate it in Firefox on Desktop when resizing the browser to go to mobile view.

Change the date but the field is still focused with a purple border and then directly click save transaction.
The date then is the date it was when i entered the field and it got the purple border.

iOS i can not test.

<!-- gh-comment-id:1883618262 --> @HansiWursti commented on GitHub (Jan 9, 2024): I can replicate it in Firefox on Desktop when resizing the browser to go to mobile view. Change the date but the field is still focused with a purple border and then directly click save transaction. The date then is the date it was when i entered the field and it got the purple border. iOS i can not test.
GiteaMirror commented 2026-04-14 17:57:52 -05:00
Author
Owner
Copy Link

@pascalxricher commented on GitHub (Jan 9, 2024):

EDIT: Replaced 'Save' by 'Add Transaction '.

Ok, I understand what I did wrong... In the PWA, when I did these steps with the previous version, the date was correctly updated, contrary of the newest version :

  1. Go in an account.
  2. '+' sign to add a transaction.
  3. Specify the amount.
  4. Specify the category.
  5. Click the date field, select a date in the past, and click the 'configure' button to confirm the date.
  6. Leave the focus on the date field.
  7. Click on Add Transaction.
  8. The saved date is the date of the day instead of the selected date. In the previous version, the selected date was saved even if the focus was on the field.

It's probably then NOT a bug, but a change in how to use the screen...

<!-- gh-comment-id:1883905136 --> @pascalxricher commented on GitHub (Jan 9, 2024): EDIT: Replaced 'Save' by 'Add Transaction '. Ok, I understand what I did wrong... In the PWA, when I did these steps with the previous version, the date was correctly updated, contrary of the newest version : 1) Go in an account. 2) '+' sign to add a transaction. 3) Specify the amount. 4) Specify the category. 5) Click the date field, select a date in the past, and click the 'configure' button to confirm the date. 6) Leave the focus on the date field. 7) Click on Add Transaction. 8) The saved date is the date of the day instead of the selected date. In the previous version, the selected date was saved even if the focus was on the field. It's probably then NOT a bug, but a change in how to use the screen...
GiteaMirror commented 2026-04-14 17:57:52 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Jan 9, 2024):

I have tried again and again on iOS (in portrait mode/mobile view) and I’m still not seeing this. Whenever and however I change the date of the new transaction it always sticks. I’m also slightly puzzled in that I see”Done” rather than “Configure” and “Add Transaction” and not “Save”.

EDIT at LAST I can reproduce this! I went on to my iPad and then put two apps side by side. I then narrowed the size of the Actual view until it went into mobile view mode and then I narrowed it still further. Now, when I add a transaction, in my usual way, the date change does not save even after “Done” UNLESS I click away from the date box before adding the transaction. Since I cannot reproduce this in any circumstances on my iPhone 15 Pro Max it makes me wonder if it could have anything to do with screen size/ the way Actual displays on different mobile devices?

My laptop was not to hand but this would correspond with the experience mentioned above on reducing the window size in Firefox on desktop.

<!-- gh-comment-id:1883915354 --> @Kidglove57 commented on GitHub (Jan 9, 2024): I have tried again and again on iOS (in portrait mode/mobile view) and I’m still not seeing this. Whenever and however I change the date of the new transaction it always sticks. I’m also slightly puzzled in that I see”Done” rather than “Configure” and “Add Transaction” and not “Save”. EDIT at LAST I can reproduce this! I went on to my iPad and then put two apps side by side. I then narrowed the size of the Actual view until it went into mobile view mode and then I narrowed it still further. Now, when I add a transaction, in my usual way, the date change does not save even after “Done” UNLESS I click away from the date box before adding the transaction. Since I cannot reproduce this in any circumstances on my iPhone 15 Pro Max it makes me wonder if it could have anything to do with screen size/ the way Actual displays on different mobile devices? My laptop was not to hand but this would correspond with the experience mentioned above on reducing the window size in Firefox on desktop.
GiteaMirror commented 2026-04-14 17:57:53 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Jan 10, 2024):

The way the fields work in the mobile transaction page is that they need to be put out of focus in order for the new values to be applied. Meaning, click/tap out of field after editing it so that it is not focused and then proceed to save/add the transaction.

<!-- gh-comment-id:1884064171 --> @joel-jeremy commented on GitHub (Jan 10, 2024): The way the fields work in the mobile transaction page is that they need to be put out of focus in order for the new values to be applied. Meaning, click/tap out of field after editing it so that it is not focused and then proceed to save/add the transaction.
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#15103
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?