mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 14:43:36 -05:00
[Bug]: nYnab Import Produces "An unknown error occurred while importing. Please report this as a new issue on Github." #1123
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1123
Reference in New Issue
Block a user
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?
Originally created by @al3x1337 on GitHub (May 30, 2024).
Verified issue does not already exist?
What happened?
Trying to import a nYnab budget file having used both the yNab Exporter and the API method across both a self-hosted instance on Unraid with HTTPS and Pikapods,
I've checked Actual-Server's directory and unraid container logs for any insight but could not find detailed logs.
What error did you receive?
this An unknown error occurred while importing. Please report this as a new issue on Github. error occurs across both budget files that I used.
Where are you hosting Actual?
Unraid and Pikapods
What browsers are you seeing the problem on?
Firefox, Firefox Private Browsing
@MatissJanis commented on GitHub (Jun 16, 2024):
👋 Thanks for the report. Would you mind providing an example file that we could use to reproduce the issue? Without the ability to reproduce there isn't much we can do to assist.
@al3x1337 commented on GitHub (Jul 1, 2024):
Thank you for the comment. What I did and was use the Console in my brower's Dev Tools to read out what the error was, after realizing that is how to access any kind of logging.
In my case I had a Category Group named "Income" that was creating a conflict. Resolved the import error.
@youngcw commented on GitHub (Jul 1, 2024):
@al3x1337 Thanks for looking into it. I think that issue got fixed, in recent release. If you still have that old export you could try again and see if its still broken
@al3x1337 commented on GitHub (Jul 1, 2024):
@youngcw For some context, I self-hosted on Unraid and did not see an update for Actual Server. Still, I added :latest to the repo tag and forced an update to make sure I'm on the latest version v24.6.0. After that I used the YNAB JSON website to export my Budget json before encountering the Import error.
Coincidentally all 3 of my existing budgets had the Income category so it wasn't until I created a new budget that I realized something within my Budget is breaking the importer. Glad I came across a way to access the logs since that gave away the smoking gun as to what the issue was.