Environment:
-
Setup: Self-hosted (VPS via any-sync-dockercompose)
-
Desktop Version: v0.55.4
-
iOS Version: v0.46.1
Description:
I am experiencing parsing and rendering issues on the iOS app when syncing data created on the newer Desktop version. The actual node syncing works perfectly, but the iOS app fails to interpret the newer data structures for queries and views.
Bug 1: Query filters do not apply on iOS
When I configure specific query filters on the Desktop app, they work flawlessly there. However, on the iOS app, these filters are completely ignored, and the query shows unfiltered results.
Bug 2: Inline page queries show incorrect/duplicate views
If I create multiple distinct inline page queries with different views (e.g., one List view, one Board view) on the Desktop, the iOS app fails to differentiate them. Instead, it renders them as identical, duplicated default views.
Troubleshooting steps already taken:
-
Updated the self-hosted backend (pulled the latest
any-sync-dockercomposerepo, restarted the Docker stack). -
Deleted and completely reinstalled the iOS app to clear any local cache.
-
Re-imported the
client.ymland logged in via Recovery Key to force a fresh sync from the updated nodes.
Steps to Reproduce:
-
On Desktop (v0.55.4), create a new Set or Collection with a few objects and assign different properties/tags to them.
-
Create an Inline Page Query and apply a specific filter (e.g., “Tag is X”). Verify that the filter works correctly on Desktop.
-
On the same page, create a second Inline Page Query but select a completely different layout (e.g., make the first one a “List” and the second one a “Board” or “Gallery”).
-
Wait for the node sync to complete.
-
Open the exact same page on the iOS app (v0.46.1).
Expected Result: The iOS app respects the filter (showing only specific objects) and renders the two inline queries with their distinct layouts (List and Board).
Actual Result: The iOS app ignores the filter (showing all objects in the set) and renders both inline queries identically, defaulting to the same basic view.
Conclusion:
This appears to be a schema mismatch between Desktop v0.55.4 and iOS v0.46.1. The older iOS client seemingly cannot decode the new query/view parameters introduced in the recent Desktop updates.
Are there any known workarounds to make Desktop views compatible with the current iOS version in the meantime?