Long-term library care
ManYue two-device handoff: finish one session before starting the next
Use one sample comic to verify an iPhone–iPad handoff, keep one established sync method, and compare actual scenes when checking older progress.
On this page
When an iPad opens an older place after reading on an iPhone, avoid advancing and forcing sync on both at once. Establish a sequential handoff: finish the first session and its sync, then receive and verify on the second device. This method makes observations clearer without assuming automatic conflict merging or file transfer.
Verify the same content on both devices
On both devices, compare source, edition, chapter coverage and a known scene with adjacent pages. Local files must be available independently, and server identities should match the intended account and connection. Identical covers do not rule out different pagination. Prepare readable content on both devices before testing record transfer.
Use one established sync method
Use the iCloud or WebDAV method already configured for your reading data and check that both devices target the intended account or sync location. Do not change providers during the same handoff test. Check current in-app conditions and retain an application-data backup before any uncertain initialisation. Identify which device currently holds the authoritative reading state.
Reach a clear new anchor on device one
On the first device, reach a recognisable new scene, note the chapter, and return to the shelf to end the session normally. Observe or complete the existing sync flow and record any failure. Keep the second device from advancing the sample during this step. The goal is a clear transfer, not a race between concurrent updates.
Receive on device two before reading
On the second device, let the established sync flow receive the remote state before entering the same item’s resume action. Do not advance elsewhere first. Compare the chapter and actual scene rather than just percentages. Similar temporary layouts can make the comparison easier across screen sizes. Restore the preferred layout after the anchor is confirmed.
Verify a handoff in the opposite direction
Advance briefly on device two, end the session, complete sync and reverse the sequence back to device one. Two successful directions verify this particular content and environment, not every source or conflict case. Keep filenames, entries, downloads and server scans unchanged while testing so record-transfer problems remain distinguishable from content changes.
Investigate an old position in three layers
Check item and edition identity first, then whether the sender finished and synced, then whether the receiver obtained the update. Do not alternate upload and download blindly. Preserve both current states and write down their scene anchors before choosing the desired record using the current recovery guidance. Share redacted status and steps rather than credentials or private backups.
Use a short handoff habit
For everyday use, end the session, check for sync errors, then inspect the actual scene on the receiving device. After extended offline use, decide which current state you intend to retain before transferring. Prepare comic files separately for travel and keep data backups and originals; sync is not an immutable history archive.
Questions and completion criteria
What if percentages match but scenes differ? Check edition, identity and layout. What happens during simultaneous reading? That depends on the current implementation and is outside this sequential test. Finish with correct new anchors in both directions, readable files on each device and an understood sync setup. Repeat the full comparison when content or conditions materially change.
Related guides and sources
ManYue iCloud sync: move reading progress and shelves to another device; ManYue WebDAV data sync: use a dedicated folder and choose the first direction.
Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.