Skip to content

App won't sync / changes not showing

Quok syncs continuously - a change on one device normally shows up everywhere within a second or two. It also keeps working offline, which is usually what’s going on when things look “stuck”.

Quok tells you when it’s offline:

  • Mobile: a chip in the top bar shows when you last synced. If changes are waiting to go out, it grows a badge with the count. Tap the chip to force a connection check.
  • Web: a banner appears at the top - “Offline - last synced X ago”, with a count of changes waiting to sync.

No chip, no banner? You’re online and synced - see If you’re online and still not seeing a change below.

Without a connection, Quok keeps your calendar and lists readable from its local copy, and anything you add or change is queued on the device. The moment you’re back online, queued changes send automatically, in order - nothing is lost, and duplicates can’t happen even if the connection drops mid-send.

So “my change isn’t on my partner’s phone” while the offline chip is showing just means: reconnect, and it will be. The full tour of what works without a connection: Offline mode.

  1. Check the device’s connection - Wi-Fi or mobile data actually working? (Hotel and café Wi-Fi often needs a login page before real traffic flows.)
  2. On mobile, tap the sync chip to re-probe the connection.
  3. On web, reload the page once you’re back online.

If you’re online and still not seeing a change

Section titled “If you’re online and still not seeing a change”
  • Give it a few seconds - live updates occasionally take a moment to catch up, and the app refreshes its data automatically when the connection is re-established.
  • On mobile, tap the sync chip; on web, reload the tab. Both force a fresh fetch.
  • Make sure both devices are signed in to the same family, and that the change was actually saved on the other device (its own offline chip may be showing).

A change the server rejects (for example, you no longer have permission for it) is dropped from the queue and the app returns to what the server has - that’s expected, not data loss. If the app asks you to sign in again after being offline for a long stretch, sign in and your queued changes send as soon as you do.

There’s a cap of 50 queued changes per device; if you somehow hit it, get online once and the queue drains.

Force-quit and reopen the app (or hard-reload the browser tab). If sync still won’t move, contact support and tell us what the sync chip or banner says - that detail localizes the problem fast.