github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #1296] [Bug]: Sync error after upgrade to v23.7.1 #42146

New Issue
Closed
opened 2026-04-26 01:46:49 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-26 01:46:49 -05:00
Owner
Copy Link

Originally created by @joel-jeremy on GitHub (Jul 5, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1296

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Upgraded to v23.7.1 and now I'm getting this error when I'm syncing:
image

What error did you receive?

No response

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @joel-jeremy on GitHub (Jul 5, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1296 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Upgraded to v23.7.1 and now I'm getting this error when I'm syncing: ![image](https://github.com/actualbudget/actual/assets/20313680/3cabc44c-8f68-45ad-9bfc-1b48c975ebfc) ### What error did you receive? _No response_ ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bug label 2026-04-26 01:46:49 -05:00
GiteaMirror commented 2026-04-26 01:46:51 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jul 5, 2023):

Did you previously run 23.7.0?

<!-- gh-comment-id:1622558010 --> @j-f1 commented on GitHub (Jul 5, 2023): Did you previously run 23.7.0?
GiteaMirror commented 2026-04-26 01:46:51 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Jul 5, 2023):

Yes, I did. I was able to workaround the problem by exporting my 23.7.0 file and importing on 23.7.1.

<!-- gh-comment-id:1622588324 --> @joel-jeremy commented on GitHub (Jul 5, 2023): Yes, I did. I was able to workaround the problem by exporting my 23.7.0 file and importing on 23.7.1.
GiteaMirror commented 2026-04-26 01:46:52 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jul 6, 2023):

I managed to reproduce a version of this.

Steps:

  1. downgrade to a older version (for example v23.4.0)
  2. create a new budget
  3. create a new account
  4. sync it to the server
  5. upgrade to latest version
  6. start the server
  7. local version will load without issues
  8. open a new incognito window and connect to the server
  9. download the budget
  10. it will break

Issue:

Error: no such column: type in table accounts
<!-- gh-comment-id:1624239294 --> @MatissJanis commented on GitHub (Jul 6, 2023): I managed to reproduce a version of this. Steps: 1. downgrade to a older version (for example v23.4.0) 2. create a new budget 3. create a new account 4. sync it to the server 5. upgrade to latest version 6. start the server 7. local version will load without issues 8. open a new incognito window and connect to the server 9. download the budget 10. it will break Issue: ``` Error: no such column: type in table accounts ```
GiteaMirror commented 2026-04-26 01:46:52 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jul 6, 2023):

The very easiest solution we could do is: create a new migration that adds back the type field. We won't be using it.. but it would solve this problem.

<!-- gh-comment-id:1624250127 --> @MatissJanis commented on GitHub (Jul 6, 2023): The very easiest solution we could do is: create a new migration that adds back the `type` field. We won't be using it.. but it would solve this problem.
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#42146
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?