ManYue: Verify identity and progress when opening local comics from Home

ManYue 2.0.4 publicly states that local comics on Home can open directly in the reader. Fewer steps help continuation, but namesakes, old progress and different card regions still need checking. Use two clearly marked small samples to record where you tapped, which entry opened and where it started. Do not assume that every card on Home follows the same navigation path.

Give two samples visible identity markers

Create two short comics, writing Book A and Book B visibly on their covers and every page, and retain originals. Similar titles can test namesake risks, but content markers must be clearly different. If title editing is unavailable, name the files before import. Record filename, import source, total page count and marker locations. Do not rename or repeatedly import an active serial library for this exercise. The samples do not prove that the app distinguishes every namesake; they let you identify the opened book after a navigation step without guessing from cover colour.

Establish a known position from the local shelf

After normal import, open both books from the local shelf and verify their first-page A/B markers and total page counts. Leave Book A at page three and Book B at page five; these numbers apply to self-made samples with at least six pages. With fewer pages, choose two different visible anchors. Leave the reader and record the content at each position. Do not rely solely on percentages, which may be rounded for short books. Establishing this baseline before testing Home separates selection of the wrong book from progress that had already failed to save.

Distinguish the shelf entry from an individual cover

On Home, locate the local-shelf area and observe whether its heading, count and individual covers are visible. In the current local implementation, the overall shelf entry and individual covers have different actions: the former opens the shelf, while a cover can open its reader directly. Installed layouts may differ, so record the actual tapped region instead of blindly using fixed coordinates. If the sample cover is absent on Home, locate it through the normal shelf entry before declaring direct reading broken. Do not group history continuation, favourites or remote recommendations under the name local-cover entry.

Check both book identity and position after tapping

Tap Book A’s individual cover and record whether it opens directly in the reader. First confirm the A marker, then check the earlier page-three anchor. Opening the correct book at page one means identity is correct but position needs investigation; it is not selection of the wrong book. If Book B or a remote namesake opens, preserve the tapped area and visible identity, and stop turning pages to avoid replacing more progress. Return to Home and check Book B’s page-five anchor in the same way. Keep both results. One abnormal sample does not establish that all Home entries behave incorrectly.

Check the return destination

Use a visible return method in the sample reader and record whether it returns to Home, the shelf or another page. Do not assume that the system back gesture and an in-app back button are identical. If practical, try each once and label the action clearly. If cards move after returning, re-identify the object by title and marker rather than repeatedly tapping the former screen coordinate. This check establishes which level your next continuation passes through. It does not demand preservation of every scroll position or invent a dedicated Return to Home button.

Confirm local identity during an offline check

For an offline direct-reading check, first confirm that both books are fully imported. Then, in a recoverable offline state, open them from the same local area on Home. Record A/B markers, target positions and network state. A remote namesake failing offline does not establish a local-file failure. Conversely, a local first image does not prove that the whole book is readable; check middle and final pages too. Restore network settings afterwards. If you did not perform this check, mark it unverified rather than promising offline access from a visible cover. Do not interrupt important network work merely to force completion of the exercise.

Check version and identity before treating navigation as faulty

If a cover still opens a detail page first, record the installed version, visible region and actual path, and compare the applicable public release. Do not search unfamiliar settings for an invented switch. If the entry is absent on Home, check successful import, hiding state and device identity from the local shelf. Do not refresh Home by repeatedly importing real files and creating more namesakes. If the shelf path works but Home fails, report the two shortest paths and results side by side. If both fail, inspect sample integrity and reading first rather than focusing solely on Home navigation.

Leave the app and verify continuation end to end

Finally, move Book A forward one page and record the new anchor. Leave the reader normally, then leave the app and return. Tap Book A’s cover on Home and check book identity, restoration of the new position and the eventual return destination. Preserve any difference from the previous round and its time instead of deleting a failed observation. Completion requires an actual result or explicit untested status for four items: entry region, content identity, saved position and return level. Direct reading from Home reduces steps, but does not replace basic checks of namesakes and reading progress.

Related guides and sources

ManYue per-comic preferences: change one vertical comic without changing others; ManYue reading history: find the last title and position.

Checked on November 7, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.