Sync after restoring a backup
What this does
Gets a device you’ve restored a backup onto syncing with your other devices again.
Usually there’s nothing to do. At most, the first sync asks for a PIN, once.
Before you start
- Nothing here deletes anything, and your logbook isn’t in trouble. A restored device either syncs straight away or asks to be paired once, and either is normal.
- Both devices: the restored one, and the device you want it to sync with. Same Wi-Fi, no VPN, both apps open with the profile open, both signed in to the same Aviator Archive account.
- Know which restore you ran, Replace or Merge (→ H6). It decides whether the second half of this guide applies to you at all.
Steps
- On the restored device: open Cloud-Less Sync and tap the other device in the list (→ I5). If the restored device was already a member of the logbook — the same device, with the same keys — the sync runs to Sync Successful! and you’re done.
- If a Connection Request appears on the other device: type its six digits into the Authentication Required dialog on the restored device, leave Trust this device ticked, and tap Connect (→ I4). That pairs the restored device, and it won’t ask again.
- If the restored device says “This device doesn’t have the other one in this logbook yet. Start the sync from the other device instead: this one will show a PIN to enter there.”: do that. On the other device, tap the restored device in its list, then type the six digits the restored device shows, with Trust this device ticked.
How to tell it worked
The sync runs to Sync Successful!, and the next one between the same two devices goes straight through with no PIN. On the restored device, Profile Settings → Account & Data → Devices shows the other device badged IN THIS LOGBOOK (→ I7).
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| The other device never appears in the list at all | A different profile, or a network problem — not the restore | Start with A2, then family 1 in I9 |
| A PIN on every sync, not only the first | Trust this device wasn’t ticked when the PIN was typed | Sync again, and leave it ticked this time (→ I4) |
| The other device was removed from this logbook, so this device won’t sync with it… | Someone removed that device under Devices (→ I7) | Start the sync from the other device. The restored device shows a PIN to type there |
| The sync finishes in a second, reporting Sent: 0 | A Replace restore brought the source device’s sync bookmarks with it | See below |
Why it sometimes asks for a PIN
Which devices may sync a logbook is part of the logbook (→ I1), but a backup can’t add one. A Merge restore and a Combine never bring a member list in from the file. A Replace restore copies the whole file, member list included, but those members only count on this device if they trace back to a pairing this device made itself. So a restored device either syncs straight away, because it was already a member, or is paired once with a PIN.
With more than two devices, pair the restored one with any one of them. Once your devices have synced, the others accept it too.
The other thing a Replace restore did
A PIN is something you can see. This one is quiet, and it only affects a Replace restore — a Merge leaves it behind.
A Replace restore copies the source device’s whole logbook file, and that file carries its bookmarks of what it had already sent each other device. So the restored device now believes it has already sent everything to devices it has never spoken to, and it sends them nothing. The symptom is a sync that succeeds instantly with Sent: 0 while the other device is plainly missing flights.
The fix is Reset Sync Status, on that device’s entry under Devices on the restored device (→ I7). It clears the inherited bookmark — or, if it can’t find it, every bookmark on the device — and tells you which.
If a flight still hasn’t moved after that, open it on the restored device, change anything, and save. The edit is newer than the inherited bookmark, so that flight goes out with the restored device’s next sync. Editing on the other device doesn’t help here — it only makes that device send its own new edit, and that device was never the one holding back.
What not to do
Don’t delete the profile and create it again. It takes the logbook with it, and it isn’t the answer to anything on this page.