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

[Bug]: Adding in really old dates causes the budget to crash. #2555

New Issue
Closed
opened 2026-02-28 20:18:50 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:18:50 -06:00
Owner
Copy Link

Originally created by @Shikogo on GitHub (Oct 20, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I was doing my budget (importing CSV, adding manual transactions, reconciling the account, etc.). When I was done and wanted to return to the main budgeting screen, the error message "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a new issue on GitHub." appeared.
I tried the following fixes with no success:
Clear local browser cache.
Reset budget cache.
Repair transactions.

The other screens seem to work. If I attempt to switch files, the whole app becomes unresponsive (get stuck in loading forever), I have to delete the browser cache to be able to redownload the file and access it again, at which point the budget screen becomes inaccessible again.

How can we reproduce the issue?

I do not know what caused this so I cannot say how to reproduce it.

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @Shikogo on GitHub (Oct 20, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I was doing my budget (importing CSV, adding manual transactions, reconciling the account, etc.). When I was done and wanted to return to the main budgeting screen, the error message "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a new issue on GitHub." appeared. I tried the following fixes with no success: Clear local browser cache. Reset budget cache. Repair transactions. The other screens seem to work. If I attempt to switch files, the whole app becomes unresponsive (get stuck in loading forever), I have to delete the browser cache to be able to redownload the file and access it again, at which point the budget screen becomes inaccessible again. ### How can we reproduce the issue? I do not know what caused this so I cannot say how to reproduce it. ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the transactionsgood first issuebug labels 2026-02-28 20:18:50 -06:00
GiteaMirror commented 2026-02-28 20:18:52 -06:00
Author
Owner
Copy Link

@Shikogo commented on GitHub (Oct 20, 2025):

Ok, I have both managed to reproduce the bug and fix it. I am able to, mostly accidentally, create extremely small dates. My Actual is set to DD.MM.YYYY format, and I am able to enter 1.1.1 for 01.01.0001. This is accepted by Actual but then breaks the front page.
I was able to recover my save file by exporting it, changing the borked date into something more reasonable, and re-zip-ing and uploading the exported file.

@Shikogo commented on GitHub (Oct 20, 2025): Ok, I have both managed to reproduce the bug and fix it. I am able to, mostly accidentally, create extremely small dates. My Actual is set to DD.MM.YYYY format, and I am able to enter 1.1.1 for 01.01.0001. This is accepted by Actual but then breaks the front page. I was able to recover my save file by exporting it, changing the borked date into something more reasonable, and re-zip-ing and uploading the exported file.
GiteaMirror commented 2026-02-28 20:18:52 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 20, 2025):

Im surprised that the date of 1.1.1 doesn't get turned into 2001 instead of 0001. Assuming post 2000 is probably the fix here.

@youngcw commented on GitHub (Oct 20, 2025): Im surprised that the date of 1.1.1 doesn't get turned into 2001 instead of 0001. Assuming post 2000 is probably the fix here.
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#2555
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?