Changelog - v1.12.7
🐛 Bug Fixes
Cloud Sync no longer gets stuck after moving a project between workspaces
Moving a project into a different workspace (or renaming a project's folder) could
silently break Cloud sync. Once that happened, all pending changes — across every
workspace, including file uploads and chat — stopped syncing and the queue kept growing
in the background, even though the app showed no obvious error.
What was happening:
- A project move was rejected by the server and quietly dropped, leaving the project in
its old workspace on the server. - Every later change to that project was then refused, and because uploads are processed
in order, that one blocked change held up the entire upload queue indefinitely.
What's fixed:
- ✅ Project moves and folder renames now sync correctly.
- ✅ A single rejected change can no longer block everything else — the app recognizes it,
sets it aside, and keeps the rest of your data flowing. - ✅ Genuine "a project with this folder already exists" conflicts now surface as a clear,
specific message instead of a generic failure.
User Benefit:
Your Cloud workspaces stay reliably in sync, even after reorganizing projects across
workspaces.
🏗️ Improvements
Better sync diagnostics
- The built-in sync health check now correctly recognizes a stalled upload queue based on
how long changes have actually been waiting, instead of under-reporting it. - Support bundles now report accurate per-table breakdowns of the pending upload queue,
making future sync issues much faster to diagnose.
📝 Notes
This is the first stable release on the 1.12.x line. The sync server fix is already live;
this app update completes the fix on the client side.
📅 Release Info
- Version: 1.12.7
- Release Date: 2026-06-27
- Previous Version: 1.12.7-beta.1
- Type: Patch Release (Stable)