Follow updates in ManYue: build a list for ongoing reading

A favorite says 'I want to keep this work'; following updates answers 'is there new content to continue reading?' ManYue provides a separate Updates entry point for checking sources that supply update information. This exercise tracks one serial and establishes understandable status rather than subscribing to every favorite at once.

Choose a work with clear update information

Open a work from a comic source that is already added and reachable. Confirm that its chapter list loads and that the latest chapter name and publication time contain recognizable information. Start with a serial you are currently reading rather than testing notifications on a completed work with no update date. Sources differ in the update capabilities they provide.

Record the current latest chapter and your reading position—for example, the series is at chapter twenty and you have read through chapter eighteen. This baseline distinguishes a newly added chapter from older unread chapters. Update-following status is not download status and does not mean the app has stored every subsequent page locally.

Follow updates from the details page

Find Follow Updates or the corresponding action in the work's details and add it through the current interface. Then open Updates, confirm that the work appears, and check its source name. The same title on different sources may represent different records. Confirm that you added the one you just viewed rather than another previously favorited version.

If the details page lacks the relevant action, check whether the source supports it and whether your current entitlement allows it. Do not substitute arbitrary buttons. Favorites, Read Later, and following updates serve different purposes: long-term retrieval, planning the next reading session, and tracking serial changes. Every work does not need all three.

Manually check for updates once

Use Check Now or the current check button on the Updates page and wait for the result. Read the last-check time, pending updates, and any error explanation. The first check establishes the current state and may not immediately show new content. No red badge does not prove a malfunction; the source may genuinely have no additional content since the previous check.

If several works are being checked, let the current round finish. Repeated clicking on a slow network can make results harder to distinguish. Return to the chapter list and compare the newest chapter name rather than relying only on the Updates page count. Notifications are useful when their records agree with actual chapters.

Manage pending updates after reading

Open an updated work, continue from your progress, and return to Updates afterward to inspect its state. If Mark as Read is available, understand that it organizes update notifications; it does not prove you read every page. Use it only after confirming that the reminder is no longer needed, taking special care not to tap the page-wide Mark All as Read accidentally.

For updates you temporarily lack time to read, keep them pending or add the work to Read Later. Do not mark unread chapters as read merely to remove red badges, or you will lose a clear reminder for next time. Following updates saves you a catalog check; it does not require an empty list every day.

Limit the scope when following a group

If the page offers following a shelf group, first create a group containing only two or three serials and choose it. Check the included scope so completed works, backup sources, and temporary samples are not added unintentionally. When group membership changes, return to the Updates page and verify the actual list. The same group name does not prove unchanged contents.

When a work ends or you stop reading it, use Stop Following Updates in its update actions. This differs from deleting the comic, deleting local files, or clearing history. After stopping, confirm in Favorites or the library that records you want remain, then decide whether further cleanup is needed. You do not have to combine several distinct cleanup operations.

Understand the reasons an update check may fail

For Source Not Found, restore the relevant source before checking again. If the source does not support update checks, repeated refreshes cannot add that capability. A missing update-date message means the source lacks enough information for the same judgment. Retry network errors once the source is reachable again; failure is not confirmation that there are no updates.

If errors persist after a source changes, check its version and maintainer notes on the comic-source page first. Removal, renaming, or changed internal identifiers can invalidate an old followed item. Compare the old and new details and chapters and confirm they are the same work before changing the tracked item. Do not replace it based only on a similar cover.

Frequently asked questions

Does following updates automatically download new chapters? Update checks tell you what is new; comic pages still require a separate download. For offline reading, explicitly download and verify completion, especially before leaving home.

Does no update notification prove the author has not updated? It only describes the state supplied by the current source and check result. Unsupported sources, network failures, and delayed information can all affect the judgment. Consider the last-check time and specific error; a failed check is not reliable evidence of no updates.

Does marking an update as read change every device and server? Do not assume so. Data synchronization and server integrations cover different scopes; check the relevant feature descriptions. After organizing update notifications, inspect the corresponding service if you also need to confirm its external state rather than relying only on local-list changes.

Plan further reading

To plan your next few works, see Read-later list; for a long chapter list, use Chapter search to locate chapters. If a source cannot be checked, see Comic-source maintenance.

Sources and version

Information checked on October 23, 2026. The public release is ManYue 2.0.2, requiring iOS / iPadOS 15.0 or later. This guide is based on public feature descriptions and their entry points; available options depend on the installed version. See Official App Store description and Apple release information.