Repository navigation
Tauri: Report priority sync status - #1147
Merged
simolus3 merged 2 commits intoOct 14, 2026
Merged
Conversation
Forward the per-priority sync status from the Rust SDK (powersync 0.1.1) instead of an empty list, so hasSynced, lastSyncedAt, priorityStatusEntries and waitForFirstSync() work with the Tauri SDK.
🦋 Changeset detectedLatest commit: 2c69dbd The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
simolus3
reviewed
Oct 13, 2026
This was referenced Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to powersync-ja/powersync-native#47 and powersync-ja/powersync-native#48. The Rust SDK now exposes per-priority sync status in 0.1.1, and this forwards it to JavaScript.
Until now, the Tauri plugin always reported
priority_status: [], sohasSynced,lastSyncedAtandpriorityStatusEntrieswere unavailable anddb.waitForFirstSync()never resolved. This was documented as a current limitation in the README.This PR:
SyncStatusData::priority_status()inSerializableCoreSyncStatus, in the same shape the core extension uses (priority,last_synced_atin microseconds,has_synced), so the existing JS logic inSyncStatusSnapshotworks unchanged.PriorityStatusdoesn't implementSerialize, so this adds a smallSerializablePriorityStatuswrapper like the existing ones.powersyncto0.1.1.reports priority sync statusintegration test: it inserts aps_sync_staterow and subscribes to a stream, which makes the SDK reload the offline status. It then checkswaitForFirstSync()andlastSyncedAt.tauri-plugin-powersync.Testing:
cargo fmt --check,cargo clippy --all-targets -- -D warningsandcargo testpass. I also checked the serialized status of an offline database through the plugin's serializer and fed it intoSyncStatusSnapshot:hasSyncedbecomestrueandlastSyncedAtmatches the stored timestamp. I couldn't run the Tauri integration suite locally (on Linux, the vitest connection to the webview closes before any test runs, also on unmodifiedmain), and the test step is currently disabled in CI, so the new test hasn't run yet. Could you run it locally like for #1143?