github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #4304] [Bug]: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue. #16065

New Issue
Closed
opened 2026-04-14 19:13:15 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-14 19:13:15 -05:00
Owner
Copy Link

Originally created by @jayem5 on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4304

Image

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

This message appeared (10 times) upon launch: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue.

How can we reproduce the issue?

Launch Actual

Where are you hosting Actual?

Desktop App (Electron)

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Mac OSX

Originally created by @jayem5 on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4304 ![Image](https://github.com/user-attachments/assets/35b27d58-3d51-47fd-b2d7-1d8d42b83014) ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? This message appeared (10 times) upon launch: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue. ### How can we reproduce the issue? Launch Actual ### Where are you hosting Actual? Desktop App (Electron) ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Mac OSX
GiteaMirror added the bug label 2026-04-14 19:13:15 -05:00
GiteaMirror commented 2026-04-14 19:13:17 -05:00
Author
Owner
Copy Link

@ftbboy2115 commented on GitHub (Feb 6, 2025):

Same issue.
Windows 11
Desktop app, but browser (Edge) was also giving errors, but different ones than this.
Before updating the server this morning from 25.1.0 to 25.2.0, I exported my files to zip (SO glad I did!). I also take daily Proxmox backups, so one was run a few hours before I performed the update. Just got everything rolled back to 25.1.0 until the bugs are worked out of 25.2.0.

I appreciate the hard work of the devs! I know some are going to be frustrated, but bugs are inevitable... Imperfect people make imperfect software, and nobody's perfect 😊

But it's a good example of important backups are! I do wish there was an auto-backup & export feature prior to updates tho, instead of going into each file and manually exporting 🤔

<!-- gh-comment-id:2640599787 --> @ftbboy2115 commented on GitHub (Feb 6, 2025): Same issue. Windows 11 Desktop app, but browser (Edge) was also giving errors, but different ones than this. Before updating the server this morning from 25.1.0 to 25.2.0, I exported my files to zip (SO glad I did!). I also take daily Proxmox backups, so one was run a few hours before I performed the update. Just got everything rolled back to 25.1.0 until the bugs are worked out of 25.2.0. I appreciate the hard work of the devs! I know some are going to be frustrated, but bugs are inevitable... Imperfect people make imperfect software, and nobody's perfect 😊 But it's a good example of important backups are! I do wish there was an auto-backup & export feature prior to updates tho, instead of going into each file and manually exporting 🤔
GiteaMirror commented 2026-04-14 19:13:17 -05:00
Author
Owner
Copy Link

@ftbboy2115 commented on GitHub (Feb 6, 2025):

Just ran through some testing, and even with the rolled-back version, when I go to close the file, I get the error: "Something internally went wrong. You want to restart the app if anything look wrong. Please report this as a new issue on GitHub."
I'll probably start a new bug report, since it looks like a different error.

Image

<!-- gh-comment-id:2640616916 --> @ftbboy2115 commented on GitHub (Feb 6, 2025): Just ran through some testing, and even with the rolled-back version, when I go to close the file, I get the error: "Something internally went wrong. You want to restart the app if anything look wrong. Please report this as a new issue on GitHub." I'll probably start a new bug report, since it looks like a different error. ![Image](https://github.com/user-attachments/assets/cc402ef1-daf9-495a-b06a-3c59ea971b30)
GiteaMirror commented 2026-04-14 19:13:19 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 6, 2025):

This may be fixed in the newest version v25.2.1. Can someone confirm?

<!-- gh-comment-id:2641283401 --> @youngcw commented on GitHub (Feb 6, 2025): This may be fixed in the newest version v25.2.1. Can someone confirm?
GiteaMirror commented 2026-04-14 19:13:20 -05:00
Author
Owner
Copy Link

@jayem5 commented on GitHub (Feb 7, 2025):

This may be fixed in the newest version v25.2.1. Can someone confirm?

So far so good!

<!-- gh-comment-id:2641516763 --> @jayem5 commented on GitHub (Feb 7, 2025): > This may be fixed in the newest version v25.2.1. Can someone confirm? So far so good!
GiteaMirror commented 2026-04-14 19:13:20 -05:00
Author
Owner
Copy Link

@jayem5 commented on GitHub (Feb 7, 2025):

This may be fixed in the newest version v25.2.1. Can someone confirm?

It was good. And then it happened again.

<!-- gh-comment-id:2641995268 --> @jayem5 commented on GitHub (Feb 7, 2025): > This may be fixed in the newest version v25.2.1. Can someone confirm? It was good. And then it happened again.
GiteaMirror commented 2026-04-14 19:13:21 -05:00
Author
Owner
Copy Link

@krelltunez commented on GitHub (Feb 7, 2025):

Confirmed NOT fixed in v25.2.1. I assumed that was the point of the release, but still very slow/unresponsive, cannot delete transactions, and when closing a budget I get the internal error messages like the above (15-20 errors).

<!-- gh-comment-id:2643203076 --> @krelltunez commented on GitHub (Feb 7, 2025): Confirmed NOT fixed in v25.2.1. I assumed that was the point of the release, but still very slow/unresponsive, cannot delete transactions, and when closing a budget I get the internal error messages like the above (15-20 errors).
GiteaMirror commented 2026-04-14 19:13:22 -05:00
Author
Owner
Copy Link

@ekadin-mtc commented on GitHub (Feb 7, 2025):

This may be fixed in the newest version v25.2.1. Can someone confirm?

I'm getting this error on 25.2.1 only in the PWA. The web app itself is not giving any issues.

<!-- gh-comment-id:2643798709 --> @ekadin-mtc commented on GitHub (Feb 7, 2025): > This may be fixed in the newest version v25.2.1. Can someone confirm? I'm getting this error on 25.2.1 only in the PWA. The web app itself is not giving any issues.
GiteaMirror commented 2026-04-14 19:13:22 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Feb 12, 2025):

Hi all, are you still seeing this? I can't replicate in v25.2.1 and it might have just needed the cache clearing for you.

<!-- gh-comment-id:2654815116 --> @matt-fidd commented on GitHub (Feb 12, 2025): Hi all, are you still seeing this? I can't replicate in v25.2.1 and it might have just needed the cache clearing for you.
GiteaMirror commented 2026-04-14 19:13:23 -05:00
Author
Owner
Copy Link

@ekadin-mtc commented on GitHub (Feb 16, 2025):

Hi all, are you still seeing this? I can't replicate in v25.2.1 and it might have just needed the cache clearing for you.

That may be the case. After I deleted the PWA and reinstalled it (and cleared the cache again for good measure) I have not had any issues.

<!-- gh-comment-id:2661577565 --> @ekadin-mtc commented on GitHub (Feb 16, 2025): > Hi all, are you still seeing this? I can't replicate in v25.2.1 and it might have just needed the cache clearing for you. That may be the case. After I deleted the PWA and reinstalled it (and cleared the cache again for good measure) I have not had any issues.
GiteaMirror commented 2026-04-14 19:13:24 -05:00
Author
Owner
Copy Link

@ftbboy2115 commented on GitHub (Feb 17, 2025):

I haven't seen any issues in a few days. Using both the desktop app I've not had any further issues.

<!-- gh-comment-id:2661882656 --> @ftbboy2115 commented on GitHub (Feb 17, 2025): I haven't seen any issues in a few days. Using both the desktop app I've not had any further issues.
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#16065
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?