Budgero v1.20.3 — sync can no longer replace your budget with an older copy

A device that could not open its own copy of a workspace can no longer replace the copy on the server, and error reports now show the real cause of a failure.

Fixed

• Sync never replaces a newer snapshot with an older one. If a browser could not read its stored copy of a workspace, it started again from an empty copy and could upload that to the server before catching up, replacing the full snapshot. The server now refuses any snapshot that is older than the one it holds, and a device only uploads after it has caught up with all changes. Your change history on the server was never affected, so devices that already have your budget keep it.

Improved

• Error reports show the real cause. Budgero Cloud error reports now include the underlying error behind a failure (for example a storage or network error), the state of the app at that moment as fixed values (such as whether sync was connected and the storage type) and a random id for the visit that links a report to the server log of the same requests. Still never your data, amounts or any message text. The privacy policy describes the addition; self-hosted Budgero still sends nothing.
• Safer server logs. The server no longer writes sign-in tokens into its logs when a sync connection is refused.

Full notes: github.com/tombadilo-bombadilo/budgero/releases/tag/v1.20.3