Cloud sync not working

[jayegles]

If I stop an episode for example at minute 20 and finish it later on device A, device B ist still showing the episode to resume at minute 20 instead of starting the next episode.

[ProdigyV21]

Fixed and will ship in v1.9.8.

What was wrong

RealtimeSyncManager only subscribed to one Supabase realtime channel: account_sync_state. But playback progress is written directly to a different table — watch_history — every ~10 seconds during playback. The account_sync_state snapshot was only pushed on pause/stop/end, which meant a user actively watching on device A could update the shared position on Supabase every 10 seconds while device B had no realtime signal and only saw the new position after manually reopening Home or after the 5-minute periodic fallback fired.

Your exact scenario: finishing or advancing an episode on device A, then device B still showing the old resume position.

The fix

Landed in #130 (merged to main):

1. Second realtime channel for watch_history INSERT + UPDATE events on the same WebSocket, filtered by user_id. When it fires, the manager emits on a watchHistoryEvents SharedFlow that HomeViewModel collects and uses to trigger a lightweight Continue Watching refresh. Does NOT trigger a full cloud snapshot pull — that would be wasteful for a single-row position update.

2. 5-second debounce to coalesce bursts — watch_history fires every ~10s during active playback, so without this a binge-watching user on device A would trigger a Home refresh on every other device every 10 seconds.

3. Self-echo protection — WatchHistoryRepository.saveProgress() marks a local-write timestamp on the realtime manager, and the manager skips emissions that look like they came from our own recent write within 3 seconds. Prevents device A from pointlessly refreshing its own Continue Watching row while actively watching.

4. Periodic fallback shortened from 5 minutes to 90 seconds, so users on flaky connections who miss a realtime event still see fresh data within a reasonable window.

Requires ARVIO Cloud sign-in

Cross-device sync only works when both devices are signed into ARVIO Cloud. Device-only mode isn't affected by this change (nothing to sync across).

Testing

Please verify on v1.9.8:

1. Sign in on two devices.
2. Start an episode on device A.
3. On device B, open Home and note the current resume position in Continue Watching.
4. Let device A play for 30+ seconds.
5. On device B (without touching anything), Continue Watching should refresh within ~10 seconds of device A's next watch_history update.
6. Finish the episode on device A entirely. Device B should move to the next episode within ~10 seconds.

If the resume position still doesn't propagate on 1.9.8, please open a new issue with:

• Both device models
• Whether they're both signed into ARVIO Cloud under the same account
• Rough timeline of what happened on which device

Closing as resolved.