[GH-ISSUE #7112] [Bug]: There was an unrecoverable error in the UI. Sorry! #52099

Closed
opened 2026-04-30 20:16:10 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @ZygarDude on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7112

What happened?

Both client and server versions are: v26.2.1

Image

Fatal Error
There was an unrecoverable error in the UI. Sorry!

If this error persists, please get in touch so it can be investigated.
Restart app
Show Error
TypeError: Cannot read properties of null (reading 'getTime') at https://xxx/static/js/usePayeeRuleCounts.iQ3j4ESH.chunk.js:1:1071 at Array.sort () at https://xxxxx/static/js/usePayeeRuleCounts.iQ3j4ESH.chunk.js:1:1030 at Object.mG [as useMemo] (https://xxxxx/static/js/index.B1K79Cio.js:9:58028) at En.useMemo (https://xxxxxx/static/js/index.B1K79Cio.js:2:42509) at ce

How can we reproduce the issue?

Seems to happen when I do anything w/ the accounts. Only when I remove /accounts/* from the URL may I get back to the main screen but the issue persists when I'm trying to work w/ the accounts, including importing from SimpleFI.

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Brave & Edge

Operating System

MacOS

Originally created by @ZygarDude on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7112 ### What happened? Both client and server versions are: v26.2.1 <img width="535" height="333" alt="Image" src="https://github.com/user-attachments/assets/dc0bb89f-a8d0-48d4-9d09-70aa028b2a34" /> Fatal Error There was an unrecoverable error in the UI. Sorry! If this error persists, please get [in touch](https://actualbudget.org/contact) so it can be investigated. Restart app Show Error TypeError: Cannot read properties of null (reading 'getTime') at https://xxx/static/js/usePayeeRuleCounts.iQ3j4ESH.chunk.js:1:1071 at Array.sort (<anonymous>) at https://xxxxx/static/js/usePayeeRuleCounts.iQ3j4ESH.chunk.js:1:1030 at Object.mG [as useMemo] (https://xxxxx/static/js/index.B1K79Cio.js:9:58028) at En.useMemo (https://xxxxxx/static/js/index.B1K79Cio.js:2:42509) at ce ### How can we reproduce the issue? Seems to happen when I do anything w/ the accounts. Only when I remove /accounts/* from the URL may I get back to the main screen but the issue persists when I'm trying to work w/ the accounts, including importing from SimpleFI. ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Brave & Edge ### Operating System MacOS
GiteaMirror added the needs infobug labels 2026-04-30 20:16:10 -05:00
Author
Owner

@ZygarDude commented on GitHub (Mar 6, 2026):

Still happening after upgrading to v26.3.0

<!-- gh-comment-id:4011843652 --> @ZygarDude commented on GitHub (Mar 6, 2026): Still happening after upgrading to v26.3.0
Author
Owner

@ZygarDude commented on GitHub (Mar 9, 2026):

I'm a bit dismayed no one has replied. I've since tried the following but to no avail:

  • Unlinked all accounts from SimpleFIN.
  • Restarted the PikaPod.
  • Reset the budget cache.
  • Repaired the transactions.

What else can I try?

Thx.

<!-- gh-comment-id:4023469271 --> @ZygarDude commented on GitHub (Mar 9, 2026): I'm a bit dismayed no one has replied. I've since tried the following but to no avail: - Unlinked all accounts from SimpleFIN. - Restarted the PikaPod. - Reset the budget cache. - Repaired the transactions. What else can I try? Thx.
Author
Owner

@joel-jeremy commented on GitHub (Mar 9, 2026):

Can you try exporting the budget and then reimport as a new budget afterwards?

<!-- gh-comment-id:4027163847 --> @joel-jeremy commented on GitHub (Mar 9, 2026): Can you try exporting the budget and then reimport as a new budget afterwards?
Author
Owner

@ZygarDude commented on GitHub (Mar 12, 2026):

Can you try exporting the budget and then reimport as a new budget afterwards?

Hi, @joel-jeremy thx for replying. I tried doing that this morning but am seeing the same error on the new budget file.

<!-- gh-comment-id:4046407808 --> @ZygarDude commented on GitHub (Mar 12, 2026): > Can you try exporting the budget and then reimport as a new budget afterwards? Hi, @joel-jeremy thx for replying. I tried doing that this morning but am seeing the same error on the new budget file.
Author
Owner

@youngcw commented on GitHub (Mar 17, 2026):

This maybe is a schedule problem. Do any of your schedules fail if you open them or try to post them?

<!-- gh-comment-id:4076380781 --> @youngcw commented on GitHub (Mar 17, 2026): This maybe is a schedule problem. Do any of your schedules fail if you open them or try to post them?
Author
Owner

@ZygarDude commented on GitHub (Mar 18, 2026):

This maybe is a schedule problem. Do any of your schedules fail if you open them or try to post them?

Hi, @youngcw, appreciate you replying. I ended up figuring it out after a few hours of deep troubleshooting. It turned out to be related to one of my accounts. Whenever I would go that account, the fatal error would appear. When I would go to the overall account list (that included said account, of course), the fatal error would appear. I ended up force closing that account which created a bunch of uncategorized entries. I followed the documentation to move those entries into a temporary "holding" category which I then hid. I then recreated the account from scratch and was able to set it back up again with SimpleFI integration. I then had to redo the schedules to point to said new account. Now everything is back up and running as it should.

I wish I knew exactly what caused the error so I could share it w/ the Dev team. I have a feeling it was syntax or character related and could have been from the SimpleFI integration importing bad data from the account bank itself.

Long reply, I know, but figured I'd add this context for historical purposes, especially since it was a bit of a painful ordeal, affecting all accounts in some fashion.

I'll go ahead and close it out.

Thx!

<!-- gh-comment-id:4082774642 --> @ZygarDude commented on GitHub (Mar 18, 2026): > This maybe is a schedule problem. Do any of your schedules fail if you open them or try to post them? Hi, @youngcw, appreciate you replying. I ended up figuring it out after a few hours of deep troubleshooting. It turned out to be related to one of my accounts. Whenever I would go that account, the fatal error would appear. When I would go to the overall account list (that included said account, of course), the fatal error would appear. I ended up force closing that account which created a bunch of uncategorized entries. I followed the documentation to move those entries into a temporary "holding" category which I then hid. I then recreated the account from scratch and was able to set it back up again with SimpleFI integration. I then had to redo the schedules to point to said new account. Now everything is back up and running as it should. I wish I knew exactly what caused the error so I could share it w/ the Dev team. I have a feeling it was syntax or character related and could have been from the SimpleFI integration importing bad data from the account bank itself. Long reply, I know, but figured I'd add this context for historical purposes, especially since it was a bit of a painful ordeal, affecting all accounts in some fashion. I'll go ahead and close it out. Thx!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#52099