[Bug]: We had problems syncing your changes. Please report this as a bug by opening a GitHub issue.

[jayem5]

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

[ftbboy2115]

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 🤔

[ftbboy2115]

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.

[youngcw]

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

[jayem5]

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

So far so good!

[jayem5]

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

It was good. And then it happened again.

[krelltunez]

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).

[ekadin-mtc]

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.

[matt-fidd]

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.

[ekadin-mtc]

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.

[ftbboy2115]

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