You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Divergence] Native SDK exposes per-priority sync status and global has_synced/last_synced_at (powersync-native #48) #692
What's changing: The native/Rust SDK adds SyncStatusData::priority_status() and priority_status_for(priority), returning a new PriorityStatus type with has_synced() and last_synced_at(). It also adds global has_synced() and last_synced_at() on SyncStatusData, derived from these entries, so apps can check whether the initial sync has completed without tracking individual Sync Streams. The change is unreleased (changelog entry "0.1.1").
High priority — existing docs are now inaccurate or incomplete
None identified.
For reviewer consideration — worth documenting
Rust SDK Reference (https://docs.powersync.com/client-sdks/reference/rust): the page does not describe sync status. It links to Usage Examples for sync status and initial sync, so the new has_synced(), last_synced_at() and per-priority status have no coverage for Rust yet.
Filed automatically by Claude Code (claude-sonnet-5-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.
[Status Update] Source PR powersync-ja/powersync-native#48 is now merged on 2026-10-12.
Documentation updates can be published after the change ships in a release.
Related PR powersync-ja/powersync-js#1147 (merged 2026-10-14) forwards the Rust SDK's per-priority sync status through the Tauri plugin, so hasSynced, lastSyncedAt, and priorityStatusEntries now work on Tauri and waitForFirstSync() resolves. It is the same feature surfaced in another SDK. One newly affected page: Tauri SDK Reference (https://docs.powersync.com/client-sdks/reference/tauri), whose "Limitations" section says the Rust SDK does not provide lastSyncedAt, hasSynced, and priorityStatusEntries on SyncStatus and tells readers to use SyncStatus.forStream instead. That statement is now inaccurate once the change is released.
Activity
benitav commentedon Oct 13, 2026
[Status Update] Source PR powersync-ja/powersync-native#48 is now merged on 2026-10-12.
Documentation updates can be published after the change ships in a release.
Generated by Claude Code
benitav commentedon Oct 14, 2026
@simolus3 can you check this and close this issue if you think it's unnecessary to document? Update: I now see there is a corresponding Tauri/JS PR as well. Looks like the agent here missed a few recommendations in this regard or might log a separate issue, but a few places are now/soon outdated, e.g. https://docs.powersync.com/client-sdks/reference/tauri#limitations and examples on https://docs.powersync.com/client-sdks/usage-examples#accessing-powersync-connection-status-information
benitav commentedon Oct 14, 2026
Related PR powersync-ja/powersync-js#1147 (merged 2026-10-14) forwards the Rust SDK's per-priority sync status through the Tauri plugin, so
hasSynced,lastSyncedAt, andpriorityStatusEntriesnow work on Tauri andwaitForFirstSync()resolves. It is the same feature surfaced in another SDK. One newly affected page: Tauri SDK Reference (https://docs.powersync.com/client-sdks/reference/tauri), whose "Limitations" section says the Rust SDK does not providelastSyncedAt,hasSynced, andpriorityStatusEntriesonSyncStatusand tells readers to useSyncStatus.forStreaminstead. That statement is now inaccurate once the change is released.Generated by Claude Code