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

[Bug]: Actual import error message claims errors are automatically reported #415

New Issue
Closed
opened 2026-02-28 19:03:13 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:03:13 -06:00
Owner
Copy Link

Originally created by @shall0pass on GitHub (May 29, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Found an error message that needs to be updated to point to GitHub rather than informing the user that the error is automatically reported.

FYI. This was an attempt to import a 'new' test file since the hidden category feature was added into an older PR. There should also be a note in the next release notes about a breaking change.

image

What error did you receive?

No response

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @shall0pass on GitHub (May 29, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Found an error message that needs to be updated to point to GitHub rather than informing the user that the error is automatically reported. FYI. This was an attempt to import a 'new' test file since the hidden category feature was added into an older PR. There should also be a note in the next release notes about a breaking change. ![image](https://github.com/actualbudget/actual/assets/20625555/4839d60e-6647-47bd-b020-c5f49738c347) ### What error did you receive? _No response_ ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bug label 2026-02-28 19:03:13 -06:00
GiteaMirror commented 2026-02-28 19:03:14 -06:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (May 29, 2023):

FYI. This was an attempt to import a 'new' test file since the hidden category feature was added into an older PR. There should also be a note in the next release notes about a breaking change.

Currently, we do not support reverting migrations that have been applied to a file. That means that if you run a budget file with a newly added migration, it can no longer be loaded in a previous Actual version. I’m not sure how we can best message this, since whether or not a release includes new migration(s) is generally independent of what new features it has (e.g. Nordigen integration requires no migration)

@j-f1 commented on GitHub (May 29, 2023): > FYI. This was an attempt to import a 'new' test file since the hidden category feature was added into an older PR. There should also be a note in the next release notes about a breaking change. Currently, we do not support reverting migrations that have been applied to a file. That means that if you run a budget file with a newly added [migration](https://github.com/actualbudget/actual/tree/master/packages/loot-core/migrations), it can no longer be loaded in a previous Actual version. I’m not sure how we can best message this, since whether or not a release includes new migration(s) is generally independent of what new features it has (e.g. Nordigen integration requires no migration)
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
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#415
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?