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

[GH-ISSUE #3263] [Bug]: Fatal Error on iOS mobile when browsing account #8275

New Issue
Closed
opened 2026-04-10 18:28:43 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-10 18:28:43 -05:00
Owner
Copy Link

Originally created by @bobokun on GitHub (Aug 14, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3263

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

When browsing one of my accounts in mobile view.
image

Clicking on restart app it still receives this error. It only happens on one account (the other accounts seem fine)

Show Error

S3@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:92755
Gn@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:93003
@https://actual.url.com/static/js/index.Nj1ZcoBw.js:222:29699
nw@https://actual.url.com/static/js/index.Nj1ZcoBw.js:57:19540
gx@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:3141
cD@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:39779
CN@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:39707
Gp@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:39559
Ex@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:35923
sD@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:34872
I@https://actual.url.com/static/js/index.Nj1ZcoBw.js:44:1553
R@https://actual.url.com/static/js/index.Nj1ZcoBw.js:44:1915

This only happens on mobile view and does not crash in the browser.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Safari

Operating System

Mobile Device

Originally created by @bobokun on GitHub (Aug 14, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3263 ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? When browsing one of my accounts in mobile view. ![image](https://github.com/user-attachments/assets/eff5318e-4fb8-4dee-80fc-44f9c961bb9a) Clicking on restart app it still receives this error. It only happens on one account (the other accounts seem fine) Show Error ``` S3@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:92755 Gn@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:93003 @https://actual.url.com/static/js/index.Nj1ZcoBw.js:222:29699 nw@https://actual.url.com/static/js/index.Nj1ZcoBw.js:57:19540 gx@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:3141 cD@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:39779 CN@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:39707 Gp@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:39559 Ex@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:35923 sD@https://actual.url.com/static/js/index.Nj1ZcoBw.js:59:34872 I@https://actual.url.com/static/js/index.Nj1ZcoBw.js:44:1553 R@https://actual.url.com/static/js/index.Nj1ZcoBw.js:44:1915 ``` This only happens on mobile view and does not crash in the browser. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Safari ### Operating System Mobile Device
GiteaMirror added the bug label 2026-04-10 18:28:43 -05:00
GiteaMirror commented 2026-04-10 18:28:45 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Aug 16, 2024):

I was unable to replicate this on IPhone 13 with Safari using the test budget file. Can you give more replication instructions/a budget file with the issue?

I tried:

  • Navigating to accounts
  • Refreshing on account page
  • Performing actions on the account, adding transations etc
<!-- gh-comment-id:2293525706 --> @MikesGlitch commented on GitHub (Aug 16, 2024): I was unable to replicate this on IPhone 13 with Safari using the test budget file. Can you give more replication instructions/a budget file with the issue? I tried: - Navigating to accounts - Refreshing on account page - Performing actions on the account, adding transations etc
GiteaMirror commented 2026-04-10 18:28:45 -05:00
Author
Owner
Copy Link

@bobokun commented on GitHub (Aug 16, 2024):

So after further digging through, I found the culprit and I'm not sure how this happened to begin with but I know how to fix it.

I noticed that for one of my schedules it was showing the amount 0, but opening that rule (without changing anything) and saving it fixes it.

Screenshot of the rule causing the issue:
image

open the rule and hit save (without making any changes):
image

Screenshot after hitting save:
image

The Fatal Error is no longer there anymore. I'm not sure what cause this to begin with and why it only affects this one rule but feel free to close this issue since I've resolved it.

<!-- gh-comment-id:2293595255 --> @bobokun commented on GitHub (Aug 16, 2024): So after further digging through, I found the culprit and I'm not sure how this happened to begin with but I know how to fix it. I noticed that for one of my schedules it was showing the amount 0, but opening that rule (without changing anything) and saving it fixes it. Screenshot of the rule causing the issue: ![image](https://github.com/user-attachments/assets/32e7dbf6-82f0-43ae-8d1f-a055a97a10a5) open the rule and hit save (without making any changes): ![image](https://github.com/user-attachments/assets/a9138290-cc11-450d-ba13-8ee6e9a6e53d) Screenshot after hitting save: ![image](https://github.com/user-attachments/assets/4fa17523-c34e-4cd3-8775-1b39d2102fb1) The Fatal Error is no longer there anymore. I'm not sure what cause this to begin with and why it only affects this one rule but feel free to close this issue since I've resolved it.
GiteaMirror commented 2026-04-10 18:28:45 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Aug 16, 2024):

Thanks for investigating, that's a strange one. I'll have a dig around and try to create a buggy schedule 👍

<!-- gh-comment-id:2293696076 --> @MikesGlitch commented on GitHub (Aug 16, 2024): Thanks for investigating, that's a strange one. I'll have a dig around and try to create a buggy schedule 👍
GiteaMirror commented 2026-04-10 18:28:46 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Aug 22, 2024):

Still unable to replicate it, closing as per suggestion

<!-- gh-comment-id:2303913893 --> @MikesGlitch commented on GitHub (Aug 22, 2024): Still unable to replicate it, closing as per suggestion
GiteaMirror commented 2026-04-10 18:28:46 -05:00
Author
Owner
Copy Link

@thraizz commented on GitHub (Oct 22, 2024):

Still unable to replicate it, closing as per suggestion

@MikesGlitch I have had this issue as well and was able to dig deeper, the culprit here is that the schedule is somehow created without an amount set, so it becomes this in the schedules_json_path table:
image
. This in turn crashes the mobile view by making amount be null, which will fail when Transaction.jsx tries to convert the amount to an integer here: a91a8859ab/packages/desktop-client/src/components/mobile/transactions/Transaction.jsx (L251)

I am unsure how the creation of that table happens, it looks like the query here fails under some circumstances?

<!-- gh-comment-id:2429450396 --> @thraizz commented on GitHub (Oct 22, 2024): > Still unable to replicate it, closing as per suggestion @MikesGlitch I have had this issue as well and was able to dig deeper, the culprit here is that the schedule is somehow created without an `amount` set, so it becomes this in the `schedules_json_path` table: ![image](https://github.com/user-attachments/assets/9ec18b3f-eeb8-49f6-ab1f-997189ba5359) . This in turn crashes the mobile view by making amount be `null`, which will fail when `Transaction.jsx` tries to convert the amount to an integer here: https://github.com/actualbudget/actual/blob/a91a8859ab65013c9f64567f91d7974079893019/packages/desktop-client/src/components/mobile/transactions/Transaction.jsx#L251 I am unsure how the creation of that table happens, it looks like the query [here](https://github.com/actualbudget/actual/blob/a91a8859ab65013c9f64567f91d7974079893019/packages/loot-core/src/server/schedules/app.ts#L412) fails under some circumstances?
GiteaMirror commented 2026-04-10 18:28:47 -05:00
Author
Owner
Copy Link

@bpaulien commented on GitHub (Nov 24, 2024):

https://discord.com/channels/937901803608096828/1309975044608491563

This is still happening, see above link to my issue in discord.

There was a scheduled transfer I had a rule for, but had saved with no amount, so when the window of time for the schedule do display in the account opened, it crashed because of no amount.

This happened in both accounts affected by the transfer schedule. Also, I'm on Android, so it's not just the iOS version.

I was able to fix it by the suggested way of opening and saving the schedule again.

<!-- gh-comment-id:2496068509 --> @bpaulien commented on GitHub (Nov 24, 2024): https://discord.com/channels/937901803608096828/1309975044608491563 This is still happening, see above link to my issue in discord. There was a scheduled transfer I had a rule for, but had saved with no amount, so when the window of time for the schedule do display in the account opened, it crashed because of no amount. This happened in both accounts affected by the transfer schedule. Also, I'm on Android, so it's not just the iOS version. I was able to fix it by the suggested way of opening and saving the schedule again.
GiteaMirror commented 2026-04-10 18:28:47 -05:00
Author
Owner
Copy Link

@emandel82 commented on GitHub (Mar 10, 2025):

I got this in my check register a few times in a row:
Image

I am on v25.2.1 on Pikapod.

I believe this happened each time just after I had clicked on the "Collapse split transactions" arrow button at the top of the register.

Image

Each time this happened, clearing the cache didn't work, nor did repairing the transactions. Each time, I made a copy of the file, and the copy worked fine.

<!-- gh-comment-id:2710959038 --> @emandel82 commented on GitHub (Mar 10, 2025): I got this in my check register a few times in a row: ![Image](https://github.com/user-attachments/assets/5b551a45-e342-4280-b3ed-d93a54dfe0dd) I am on v25.2.1 on Pikapod. I believe this happened each time just after I had clicked on the "Collapse split transactions" arrow button at the top of the register. ![Image](https://github.com/user-attachments/assets/b884b22b-9506-4702-a840-6b9c101ce028) Each time this happened, clearing the cache didn't work, nor did repairing the transactions. Each time, I made a copy of the file, and the copy worked fine.
GiteaMirror commented 2026-04-10 18:28:47 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 5, 2025):

These issues have now been fixed, I believe in 25.4

<!-- gh-comment-id:2942546181 --> @matt-fidd commented on GitHub (Jun 5, 2025): These issues have now been fixed, I believe in 25.4
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#8275
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?