Familiar
Docs/Help & Support

Help & Support

Troubleshooting

Work through the most common end-user issues methodically: sign-in problems, stale mobile installs, missing updates, export problems, and family-access confusion.

9 min read

Best for

Fix login issues
Resolve stale state
Know what to check first

Most issues come from browser state, device context, or account mismatch.

Use a default browser for sign-in and callback flows.

Check family context and subscription access before assuming data is missing.

In this guide

Section 01

When sign-in or callback fails

  1. 1Check that you are opening Familiar on the correct domain and not an older saved shortcut.
  2. 2Retry in Safari or Chrome directly instead of an in-app browser.
  3. 3Confirm you are using the same sign-in method you used before.
  4. 4Close stale tabs and start the sign-in flow fresh.
  5. 5If you recently changed domain or redirect settings, clear site data or reinstall the PWA.

Section 02

When data looks missing or out of date

  • Check that the correct family is selected.
  • Refresh the feature screen instead of relying on an old tab.
  • Confirm that another person did not archive, remove, or complete the item already.
  • Check whether the feature is gated by the current plan tier.

Section 03

When exports or share actions misbehave

  • Verify that planned amounts and currency are configured as expected before exporting shopping data.
  • Try exporting again after a refresh if the list changed moments before the export.
  • If a shared note link does not behave as expected, confirm that the note is actually marked shareable.

Section 04

When the mobile app feels stale

PWAs and cached browser sessions can hold onto outdated state after major changes such as a new domain, updated redirect flow, or service worker update.

  1. 1Close the installed app completely.
  2. 2Open the live site in the browser and confirm the latest behavior there first.
  3. 3Remove the old installed app if it points to an older domain or stale build.
  4. 4Install the current version again from the live site.

Do not skip the browser check

If the browser works but the installed app does not, you are usually dealing with stale local state rather than a backend outage.

Keep reading

These guides usually help next once you finish this one.