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 #1727] [Bug]: Internal Error when using Import #42303

New Issue
Closed
opened 2026-04-26 02:00:11 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-26 02:00:11 -05:00
Owner
Copy Link

Originally created by @mommyofavalor on GitHub (Sep 23, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1727

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happened!

When I went to important my normal statement I got a red "Internal Error" message on the bottom asking me to report to Github.

I tried on both Internet Explorer and Google Chrome. Both allowed me to click "import", choose my statement and then showed the outline of the grey box and a spinner and would not fully upload.

I use PikaPod.

I restarted both PikaPod and restarted my computer. Still same issue in exactly same way.

What error did you receive?

](url)
Screen Shot 2023-09-23 at 8 29 29 AM

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome

Operating System

Mac OSX

Originally created by @mommyofavalor on GitHub (Sep 23, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1727 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? A bug happened! When I went to important my normal statement I got a red "Internal Error" message on the bottom asking me to report to Github. I tried on both Internet Explorer and Google Chrome. Both allowed me to click "import", choose my statement and then showed the outline of the grey box and a spinner and would not fully upload. I use PikaPod. I restarted both PikaPod and restarted my computer. Still same issue in exactly same way. ### What error did you receive? ](url) <img width="1261" alt="Screen Shot 2023-09-23 at 8 29 29 AM" src="https://github.com/actualbudget/actual/assets/138994055/e108c82a-ff39-4de4-8e75-2539f81e1cb5"> ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Chrome ### Operating System Mac OSX
GiteaMirror added the needs infobug labels 2026-04-26 02:00:12 -05:00
GiteaMirror commented 2026-04-26 02:00:14 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Sep 23, 2023):

👋 Would you mind providing an example import file so we could reproduce? Without being able to reproduce there won't be much we can do to help you.

<!-- gh-comment-id:1732323874 --> @MatissJanis commented on GitHub (Sep 23, 2023): 👋 Would you mind providing an example import file so we could reproduce? Without being able to reproduce there won't be much we can do to help you.
GiteaMirror commented 2026-04-26 02:00:16 -05:00
Author
Owner
Copy Link

@mommyofavalor commented on GitHub (Sep 23, 2023):

Github won't let me attach a .qfx file. How can I share it with you?

<!-- gh-comment-id:1732331640 --> @mommyofavalor commented on GitHub (Sep 23, 2023): Github won't let me attach a .qfx file. How can I share it with you?
GiteaMirror commented 2026-04-26 02:00:19 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Sep 23, 2023):

You can upload .zip files.

Also: are you able to reproduce this issue in demo app. If not: then the issue has already been fixed and will be available in the v23.10.0 release.

<!-- gh-comment-id:1732334190 --> @MatissJanis commented on GitHub (Sep 23, 2023): You can upload `.zip` files. Also: are you able to reproduce this issue in [demo app](https://demo.actualbudget.org). If not: then the issue has already been fixed and will be available in the v23.10.0 release.
GiteaMirror commented 2026-04-26 02:00:20 -05:00
Author
Owner
Copy Link

@mommyofavalor commented on GitHub (Sep 23, 2023):


activity-12.qfx.zip

The demo app isnt opening for me when I click on the hyperlink in your comment. Thank you for taking the time to respond.

Is v23.10.0 already released?

<!-- gh-comment-id:1732380887 --> @mommyofavalor commented on GitHub (Sep 23, 2023): [](url) [activity-12.qfx.zip](https://github.com/actualbudget/actual/files/12707045/activity-12.qfx.zip) The demo app isnt opening for me when I click on the hyperlink in your comment. Thank you for taking the time to respond. Is v23.10.0 already released?
GiteaMirror commented 2026-04-26 02:00:21 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Sep 23, 2023):

Screenshot 2023-09-23 at 20 29 13

Your example file works on the demo app (which is using the latest changes in master branch). So it's safe to assume this has already been fixed.

v23.10.0 will be released in the first few days of September. If you prefer not to wait - you can always use the edge tag (but be prepared that things might break): https://actualbudget.org/docs/install/docker#edge-tag

<!-- gh-comment-id:1732393502 --> @MatissJanis commented on GitHub (Sep 23, 2023): <img width="870" alt="Screenshot 2023-09-23 at 20 29 13" src="https://github.com/actualbudget/actual/assets/886567/e4e4002a-2fe5-470d-8527-b1e4822b8ed7"> Your example file works on the demo app (which is using the latest changes in `master` branch). So it's safe to assume this has already been fixed. v23.10.0 will be released in the first few days of September. If you prefer not to wait - you can always use the `edge` tag (but be prepared that things might break): https://actualbudget.org/docs/install/docker#edge-tag
GiteaMirror commented 2026-04-26 02:00:22 -05:00
Author
Owner
Copy Link

@m-GDEV commented on GitHub (Sep 23, 2023):

I'm also having the same issue as the user above. I'd rather not share my .qfx file but here is the error that showed up in the console. There were two separate errors. I'm using actual v23.9.0 for both the server and client version.

I run actual-server on my own vps by cloning the repo and running yarn start. Not sure if this helps.

[Exception] TypeError: Cannot read properties of null (reading 'fallbackMissingPayeeToMemo')
    at parse-file.ts:135:33


parse-file.ts:135 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'fallbackMissingPayeeToMemo')
    at parse-file.ts:135:33

If someone knows what might be causing the issue I'd appreaciate it! Thanks.

<!-- gh-comment-id:1732412047 --> @m-GDEV commented on GitHub (Sep 23, 2023): I'm also having the same issue as the user above. I'd rather not share my .qfx file but here is the error that showed up in the console. There were two separate errors. I'm using `actual v23.9.0` for both the server and client version. I run actual-server on my own vps by cloning the repo and running `yarn start`. Not sure if this helps. ``` [Exception] TypeError: Cannot read properties of null (reading 'fallbackMissingPayeeToMemo') at parse-file.ts:135:33 parse-file.ts:135 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'fallbackMissingPayeeToMemo') at parse-file.ts:135:33 ``` If someone knows what might be causing the issue I'd appreaciate it! Thanks.
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 needs info
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#42303
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?