Maintain ManYue sources: updates, search scope and access failures

A previously working comic source can fail after website changes, expired login, or a maintainer update. ManYue source management can check updates, but updating a source, changing search scope, and deleting it are distinct actions. Identify the failing stage and choose the smallest appropriate response.

Preserve a comparable starting state

Open Comic Sources, find the problematic entry, and record its name, current version, and original release address. With a known work, check discovery, search results, chapter listing, and actual reading separately. Recording the failing step avoids describing an issue with one book as the entire source being broken.

Back up important favorites and history using available app methods, especially before deleting or replacing a source. Do not start by removing it: its identifier may connect favorites, chapters, and reading records. Readding a different source with the same name does not guarantee the same identity. Preserving the state also helps compare before and after updates.

Check for a trusted update entry point

With a valid update address, the list may show an update button and version. After a single-source update, inspect the result and version, then repeat the smallest previously failing action. Check for Updates in a source list needs a configured valid list address. Without one, do not assume the app searches the internet automatically for a same-named newer source.

For a locally imported source without a remote update address, check the original maintainer's channel for a new file. Compare release notes and compatibility requirements before importing. “Latest” in a filename is insufficient; verify version and origin. Retain update errors and avoid importing multiple uncertain files in succession, which obscures the currently used version.

After updating, retry only the original failing step

If search failed, retry the same keyword. If chapters listed but images failed, open the same chapter and page. Do not immediately test a different work after updating and use its success to declare the original problem solved. A consistent test object distinguishes changes caused by the update from differences between works.

If the maintainer requires signing in again, use the source's actual login entry. Login state and source version are often stored separately, so a script update may not restore account access automatically. Closing the password panel is not proof of login success; return to restricted content or source status to confirm.

Adjust search scope when a source should not participate

If a source is temporarily slow but you want its favorites and records, remove it from aggregate search in Search Sources settings. This is source selection for search, not a universal disable-all switch. The source may remain accessible through management or existing work entries.

Run the same aggregate-search keyword after adjustment and confirm that the source section disappears. Open the source separately to confirm it remains. This reduces waiting and noise but does not repair the source's connection. To restore search participation, add it back to scope and check a known query; reimporting the source file is unnecessary.

Consider removal only when you no longer need the source

To remove a source, choose Delete from its menu, read the confirmation, and ensure important information is backed up. Removing a source is not deleting an account on the remote website, nor does it necessarily delete every downloaded file. Different data has different ownership; inspect the local library and history separately.

When readding later, prefer the same maintainer and a compatible version, checking the source identifier. The same display name does not prove associations will return. If it is actually another source, treat it as a new entry and recheck chapter mappings and reading positions. Do not apply old page numbers directly when chapter orders differ.

Choose the next step by error type

For parsing failures, check updates and page changes; for authentication failures, account state; for timeouts, network and service availability; for one failing book, compare other works. Change one condition at a time to avoid an unexplained apparent recovery.

If the maintainer has no fix yet, continue with downloaded local content or use local import for files you are authorized to obtain. Do not bypass access controls or use unknown mirrors for temporary access. Keep the original error and version, then retest the same item when an official update arrives.

Frequently asked questions

Why is reading still unavailable when no update is found? “No new version” means only that the current update channel reports none. It does not prove website access and script parsing work. Continue checking the failing stage and maintainer guidance; an update result cannot replace a complete reading check.

Why do favorites remain after removing a source from search? Search scope affects participating sources, not the same data as favorites, history, or local files. Retaining records is appropriate when you want to stop searching a source temporarily but may use it later.

Will deleting and readding automatically fix everything? No guarantee. If the cause is a website change, network, or account, adding the same file again may produce the same error and complicate record associations. Make specific checks before taking an action with a clear purpose.

Related tutorials

To recheck the distinction between a file and URL, see Importing comic sources; for excessive search results, see Comparing aggregate search. Once the update restores access, use Series-following checklist to continue managing ongoing series.

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.