Gravify
IT EN

Help · version 0.1.13

Troubleshooting

If WhatsApp remains on the QR screen after your phone reports success, wait briefly for Gravify to confirm the connection. If it does not continue, return to Settings, reopen the connection, and retry without creating repeated requests.

If import is delayed, keep Gravify open when possible and check the expanded status details. An incomplete import does not prevent you from using Settings or viewing evidence already available. A First Light offer appears only when the imported history can produce an honest frame.

If an update check reports no connection, confirm that this computer can reach the internet and retry from License & Updates. Account links and licence activation require the hosted account service; private imported content does not leave your Personal Hub during those checks.

A notification or relationship reminder does not appear

  1. Open Settings → Notifications → Send test. On Windows there is no permission popup: access is controlled by Windows settings. If the test fails, use System settings. If submission succeeds but no banner appears, check the notification center, Do not disturb, and Gravify's banner setting.
  2. Enable Relationship Reminders on this device. System access being Allowed does not itself switch on Gravify's delivery category.
  3. Open Settings → Relationship Reminders and verify an enabled rule exists. Add labels if prompted, and heart-mark the people covered by that label.
  4. Check the condition and comparison period. A person needs comparable history in both periods and must actually meet the decline condition. A linked future encounter suppresses the reminder.
  5. Check the Reminder inbox for existing, snoozed, or resolved episodes. Delivery is limited to 09:00–20:00 local device time and one reminder per 24 hours; a snooze waits for the full configured interval.
  6. Keep the client running, or reopen it. Periodic background Hub sync does not deliver notifications from a closed client. Allow up to 15 minutes for the next clock-driven evaluation.

See Settings and customization for the full reminder and notification workflow.

Messages or media seem stuck after closing Windows

Check that background operation is enabled and the selected frequency is not Never, or use Sync now from the tray. Keep the computer awake and connected. Reopen Gravify to let the Hub import the captured events and resume media downloads; the low-consumption tray mode alone does not refresh the visible inbox or run the complete media importer.

For media, check the connector's retention choice, available disk space, and whether the original is still available from WhatsApp. Full local history is required for attachment retention. Temporary failures remain queued, and completed originals are reused after interruption. A missing or expired provider file is not proof that the message itself failed to import.

Device contacts do not appear on Windows

  1. Open Settings → Accounts & Data Sources → Device contacts. Choose Enable device contacts and confirm the explanation; a separate Windows popup is not required.
  2. Choose Refresh contacts after editing the Windows address book. If access is off, enable it again. If Windows blocks access or reading fails, use System settings and retry.
  3. If no contacts are found, check that the contacts exist in the Windows address book. Contacts available only on your phone or in an online account are not automatically copied there. Export a vCard from the source and use Accounts & Data Sources → Import files → Contact files when needed.
  4. Contacts ready to synchronize still need a connection to your Personal Hub. Existing Gravify edits take precedence over imported details.

Current location is unavailable on Windows

Open Settings → Privacy & Permissions → Test current location. This checks actual acquisition, not just permission, and saves no coordinates. If it fails, open Location system settings, check Location services and desktop-app access, and try again with Wi-Fi enabled. A cached-location result is explicitly labeled; Allowed alone does not guarantee a fresh position can be obtained.

Another Windows computer cannot connect

Follow Devices & Sync setup on both computers. Use the Hub's HTTPS Tailscale hostname, not 127.0.0.1: that address points to the computer you are currently using. Confirm both Tailscale installations are connected to the same private network and the Hub is awake with Gravify open or Always Ready enabled.

If Enable private access fails, check Tailscale's HTTPS prerequisites and whether another Serve or Funnel service already occupies port 443. Gravify leaves conflicting routes unchanged. After enabling the route, fully quit and reopen the Hub app before pairing. A configured route is not proof that the Hub is currently reachable.

An expired or reused pairing code needs a new invitation from the Hub. A workspace mismatch means the address belongs to a different archive: use Connect to another computer to create a separate replica instead of changing the current connection address. If the second computer shows its own activation page, use the existing-Hub connection button there. Pairing does not require buying a second Hub licence.

Changes waiting for review

For two versions of an edit, missing related items or possible duplicate contacts, see Review meetings, contacts and changes. You can keep a decision for later without discarding your local edit.