Loading and source-specific checks
ManYue tracker binding correction: verify main series and extras before linking
Verify tracker identity and progress units, distinguish removing a local binding from changing remote progress, and use any sync action only after checking the target.
On this page
Similar titles can refer to a main series, extra, adaptation or another edition. Inspect the mapping and remote identity before correcting a local binding. Distinguish third-party writes explicitly: unlinking should not be described as automatically undoing previous remote changes, and a test need not send progress.
Record both identities
Record local source, creator, coverage and reading anchor alongside platform and remote title. Compare medium, creator and publication scope, distinguishing adaptations and extras. Retain remote state privately for reference without exposing tokens. Identify the exact mapping before replacing anything.
Pause uncertain writes
When a target is suspect, inspect and stop unwanted updates using available controls. Do not force another sync merely to confirm an error. Authentication and entitlement do not establish correct identity. Avoid manual sync while inspecting, and keep fact-finding separate from writes to competing targets.
Check progress units
Map clear local chapter/volume boundaries to the tracker’s actual units. Directory button order, percentages, extras and omnibus packaging can differ. If a reliable mapping is unavailable, retain manual verification rather than assuming successful connection understands every edition’s structure.
Read the scope before unlinking
Remove only the identified local mapping after reading its prompt. Do not claim this deletes comics, clears history or restores earlier remote progress. Preserve the old target and state, confirm the intended list change, and inspect any remote correction separately. Account logout and deleting all mappings are different actions.
Verify a replacement candidate
Use the available add-binding flow with the correct history entry and platform. Search names or creator clues and inspect medium, edition and coverage. Stop if no valid target exists. If the local entry is missing, investigate identity/history rather than borrowing another work’s record. Re-read both names before confirming.
Inspect the new mapping before syncing
Inspect local and remote identities and the displayed sync state after binding. Creation and progress sending are distinct concepts, but check actual linkage before assuming no remote effect. A read-only inspection can stop here. For an intended update, understand units first and verify the resulting remote object and value rather than relying on a success message.
Handle old remote records separately
Inspect and correct any prior remote state through that platform’s actual controls, keeping before/after notes. A correct new binding does not erase old records or manage every account field. No comments or notifications are required. Observe subsequent ordinary use to confirm the wrong target is no longer changing.
Acceptance and ongoing checks
Finish with verified identity and units, scoped old-mapping removal, a traceable replacement and explicit remote discrepancies. Names alone are insufficient, and unlinking is not guaranteed historical undo. Recheck on meaningful source or edition changes instead of rebuilding every session or sending unverified test updates.
Related guides and sources
ManYue progress trackers: connect Bangumi or MyAnimeList and verify matches; ManYue changing comic sources: map progress by chapter and scene.
Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.