[Bug]: Closing account after CSV import (new install, first account, Mac ARM64 build) #2021

Closed
opened 2026-02-28 20:01:19 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @NEONsHONEY on GitHub (Apr 6, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Installed Actual, added first account, imported ~150 transactions from a CSV, realized I set the "starting balance" wrong and went to "close account" and got an error/crash.

How can we reproduce the issue?

How can we reproduce the issue?

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @NEONsHONEY on GitHub (Apr 6, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Installed Actual, added first account, imported ~150 transactions from a CSV, realized I set the "starting balance" wrong and went to "close account" and got an error/crash. ### How can we reproduce the issue? How can we reproduce the issue? ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the bug label 2026-02-28 20:01:19 -06:00
Author
Owner

@NEONsHONEY commented on GitHub (Apr 6, 2025):

MacOS 15.1.1 (24B91), local Actual install (no server connection).

@NEONsHONEY commented on GitHub (Apr 6, 2025): MacOS 15.1.1 (24B91), local Actual install (no server connection).
Author
Owner

@NEONsHONEY commented on GitHub (Apr 6, 2025):

Message popup: "Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a new issue on GitHub."

@NEONsHONEY commented on GitHub (Apr 6, 2025): Message popup: `"Something internally went wrong. You may want to restart the app if anything looks wrong. Please report this as a new issue on GitHub."`
Author
Owner

@NEONsHONEY commented on GitHub (Apr 6, 2025):

Looks like it can be reproduced easily. When attempting to close the account, Actual requests to select an account to transfer transactions to. Since there is no other account setup yet, there is nothing to choose. The "choose an account" popup is covering the text where there is a hyperlink to "force close", so that is not visible unless the user clicks somewhere in the popup region to dismiss the account selection popup.

At that point, clicking "force close" and accepting the warning successfully avoids the error.

This may be intended behavior, but is definitely a break in the UX flow.

@NEONsHONEY commented on GitHub (Apr 6, 2025): Looks like it can be reproduced easily. When attempting to close the account, Actual requests to select an account to transfer transactions to. Since there is no other account setup yet, there is nothing to choose. The "choose an account" popup is covering the text where there is a hyperlink to "force close", so that is not visible unless the user clicks somewhere in the popup region to dismiss the account selection popup. At that point, clicking "force close" and accepting the warning successfully avoids the error. This may be intended behavior, but is definitely a break in the UX flow.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2021