# Book Isle two-device sync handoff: check one change at a time
Language: en
Canonical: [Book Isle two-device sync handoff: check one change at a time]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-10-26T00:00:00+08:00
Modified: 2026-10-26T11:37:28+08:00
Author: Bison
Verify sync direction with a test note and chapter, preserve valuable records, and distinguish layout and edition differences from transfer problems.
English translation of the [Chinese original](), translated on 2026-10-26. Original publication dates, attribution, code and version notes are retained.
After offline reading on a phone and note editing on a tablet, preserving the right records takes a clear handoff routine. Use your WebDAV setup, two devices and one test book to observe changes in sequence. This workflow does not promise automatic merging of every conflict or treat reading-data sync as book-file transfer.
## Preserve valuable changes from both devices
Inspect recent chapters, unsynced notes and important edits on each device. Export valuable excerpts to a definite location and reopen them. Do not overwrite one device from the other before comparing content, or uninstall to resolve location differences, since local records may be lost.
Retain book files separately and confirm matching editions through contents and a quotation, beyond covers and titles. Resolve different translations or revisions before comparing progress. Identical percentages can refer to entirely different chapters in different texts, which a sync timestamp cannot explain.
## Check the same dedicated sync destination
Inspect both configurations for host, account scope and dedicated directory, ruling out one device writing an old destination. Book folders and reading-data folders serve different purposes; any browsable directory is not automatically your existing sync repository. Follow your current interface and established first-upload or download workflow.
For a moved or new directory, establish which device holds the baseline and preserve both sets of records. A few visible server files do not prove a valid complete backup. Test actual transfer rather than repeatedly overwriting unknown content; matching settings are a starting condition, not verification.
## Create one unmistakable test record on the phone
In a nonessential test book, make a second-chapter note labelled as a phone handoff check with a date. Read to a clear paragraph, record its opening words and leave the reader. Execute one deliberate sync and wait for its result, recording time and visible message without repeatedly tapping.
Until this finishes, leave that book's notes and progress unchanged on the tablet. One main writer at a time makes transfer observable. Do not use a unique important note or delete formal material to manufacture a conflict; a small reversible change can verify ordinary handoff.
## Check content on the tablet, not timestamps alone
Sync the tablet through your usual process and inspect the new note and chapter. Updated time or a success message is status evidence; the actual record is content evidence. If the note appears but the book does not open, check whether the tablet has the original file before judging record sync as entirely failed.
For a few lines' difference, compare context and layout; for a whole chapter, verify edition, direction and the phone's last saved location. Record the symptom rather than rapidly moving both devices' progress. Adding new states obscures the first issue, so hold conditions steady while investigating.
## Test the reverse handoff once
Add a differently worded test note or read a short section on the tablet, leave and sync, then sync and inspect the phone. Clear sequencing verifies both normal directions rather than expanding one successful upload into a claim about every handoff scenario.
For a conflict prompt, compare contents under the actual instructions and preserve important text before choosing. Read the operation's scope rather than assuming it affects one book or is reversible. If the result is unclear, stop adding changes and retain both versions and their execution sequence for further investigation.
## Handle reconnection one device at a time
Before offline reading, finish sync and check local files. On returning, complete one device's handoff before inspecting the other. If both gained important offline notes, preserve them separately first. A newer timestamp does not necessarily identify the more complete device because each may hold different valuable records.
Reading settings are part of the public sync scope too. Observe layout changes and retain preferences if needed. Verify statistics, labels and metadata by content rather than one matching progress value. An extra simple label can be a useful sample without changing many books at once.
## Establish a routine you can recover from
For daily handoff, leave reading and sync the current device, then sync the target before opening its reader. Preserve local records during unstable connectivity rather than resetting the whole destination for immediate visual agreement. Historical readable exports and book backups remain useful alongside sync of current changes.
Completion means both devices open the same edition, show test records in both directions and give you a clear order for preserving and diagnosing differences. This basic check does not test every outage, deletion or concurrent-edit case. Retain test notes until no longer needed and judge formal records by actual content.
## Related tutorials and sources
Continue checking your files with [local ebook basics]() and [Book Isle multiple-format management](). For reading records, see [notes and data export]().
Checked on October 26, 2026 using [Apple's public version information](): Book Isle 1.1.3 requires iOS / iPadOS 15.6 or later. Feature scope follows the [official App Store listing](). This article describes a workflow and checks; it does not claim step-by-step testing on a physical device or private server. Follow the controls in your installed version.