Skip to content

v1.0.7 — Stop auto-sync ping-pong

Latest

Choose a tag to compare

@theetaz theetaz released this 25 Apr 12:33
· 1 commit to main since this release

Critical hotfix on top of v1.0.5/6.

🛑 Auto-sync no longer runs every 3 seconds

v1.0.5 wired the local data-change signal to kick a sync 3s after every notification. The same signal is also used as a "data merged, refresh the UI" message — fired at the end of every sync and after every realtime merge. Net result: each sync scheduled the next one, forever. Users saw the sync icon spinning on what looked like a 1-second cadence as overlapping passes piled up and burnt battery.

The fix tags every `notifyLocalDataChanged` call with its source — `'user'`, `'sync'`, or `'realtime'`. The auto-sync trigger only listens for `'user'`. Sync's own tail and realtime merges still refresh the UI but no longer rearm the sync that just produced them.

No other behavioural changes.

  • Capture is still instant (v1.0.5)
  • Auto-sync still fires within 3 seconds of saving a job (v1.0.5)
  • Stuck-upload recovery + Retry button still work (v1.0.6)

Distribution

`./deploy.sh --notes "Stop auto-sync ping-pong — see GitHub release v1.0.7"`