# Troubleshoot ManYue imports: file access, formats and folder levels

Language: en
Canonical: [Troubleshoot ManYue imports: file access, formats and folder levels](<https://allluckly.cn/en/guides/manyue-import-troubleshooting/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-import-troubleshooting/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-import-troubleshooting/>)
Published: 2026-10-22T00:00:00+08:00
Modified: 2026-10-23T10:34:07+08:00
Author: Bison

Distinguish files not downloaded, format mismatches, mixed folders, insufficient storage and partial failures, using a small sample you can test repeatedly.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-import-troubleshooting/>), translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained.

An import failure does not automatically mean unsupported format or damage. A picker may return a cloud placeholder, only one item in a batch may fail, or the folder structure may be interpreted differently than expected. Change one condition at a time and retain originals to locate the failing step rather than continually generating duplicate names.

## Record the minimum useful failure information first

Record the app and iOS or iPadOS versions, extension, size, location, and whether failure occurred during selection, recognition, import, or reading. Keep the error text, concealing private paths, account details, and comic content in screenshots. There is no need to upload an entire book publicly; a small self-made sample can verify the control.

Use a small file that opens normally in Files as a control: an unencrypted comic with a simple structure or a short PDF you created. Import it through the same control. If the sample works but the original fails, examine the file first. If both fail, investigate the provider, storage, or app state.

## Layer 1: Confirm the file is actually readable

Open Files at the original location and wait for the cloud file to finish downloading. Names and thumbnails may appear before the content is local. Inspect file information or copy it to an accessible local folder, then select that copy in ManYue. This separates cloud-access issues from import parsing.

For external drives or other providers, keep the connection and authorization valid throughout import. Unplugging a drive, stopping its service, or moving the file before completion changes availability. Follow system permission prompts instead of repeatedly selecting an inaccessible item. Retain the source until the copy is verified.

## Layer 2: Inspect the extension and contents

Compare with the publicly supported CBZ, CBR, CB7, ZIP, RAR, 7z, and PDF types and ensure other data has not merely been renamed. Archives should contain readable pages or sensible chapters. Verify passwords, missing split volumes, and unusual encodings in the original tools. Do not delete or arbitrarily change extensions to force import.

If only one book fails, use a trusted tool to check its beginning, middle, and end. Listing an archive's directory does not prove every file can be extracted, just as displaying a PDF cover does not prove later pages are intact. Check the original's integrity, then create a new copy from a sound source instead of repeatedly importing damaged data.

## Layer 3: Distinguish directory recognition from batch results

For folder import, first determine whether it represents one document, chapters, or several comic files. Organize a root mixing page images and chapter subfolders into one consistent structure. If the top level contains archives and more subfolders, do not assume recursive traversal of every level. Selecting directories separately narrows the problem.

After a batch, check failures and successful-book counts. If eight of ten files succeed, verify those eight in the library and handle only the other two. Reimporting all ten creates duplicates and confusion. An error on the results screen differs from one while opening the reader: the former concerns import; the latter also requires checking page parsing and actual content.

## Layer 4: Check space and working state

Import may save files, process pages, and create usable records rather than simply add a title. Check free system storage and leave working space beyond the source file's size. Avoid simultaneously importing many huge files and cleaning the source directory; that changes several conditions at once.

Reduce the batch to one book and wait for its result. If an operation clearly stalls, record the state, leave that workflow, and retry the sample. Forced termination is not a routine import step. With repeated failures, keep verified books and give the developer a minimal reproduction rather than claiming vaguely that all files fail.

## Example and completion checks

Suppose a cloud-hosted CBR fails while a short local PDF succeeds. Fully download that same CBR and import the local copy. If it still fails, check its archive content and integrity; if it succeeds, record the original file provider and failure stage. Changing only location produces a clearer result than simultaneously changing format, filename, and reinstalling the app.

Afterward, verify beginning, middle, and end pages, persistence after reopening, and no unresolved failures. Distinguish confirmed causes from guesses in your notes; a chance success is not a universal fix for similar files.

### Should I uninstall and reinstall first?

Not as a first step. Uninstalling may affect local reading copies and app data and remove useful comparison evidence. Retain files and backups, then check sample, location, format, structure, and space before considering broader action.

### Why does one CBZ import while another does not?

The same extension does not imply identical structure, encryption, image encoding, or integrity. Compare the failed file with a successful sample to narrow the differences. One failure does not mean all CBZ files are unsupported, and matching extensions do not guarantee compatibility.

## What to read next

- [Checking format and page order](<https://allluckly.cn/en/guides/manyue-formats-and-page-order/>).
- [Organizing image folders](<https://allluckly.cn/en/guides/manyue-image-folder-import/>).
- [Back up app data before major operations](<https://allluckly.cn/en/guides/manyue-backup-and-restore/>).

## Sources and version

Checked on October 22, 2026: ManYue 2.0.2 for iPhone / iPad. Based on [the public description on the China App Store](<https://apps.apple.com/cn/app/id6753895889>), [Apple release lookup](<https://itunes.apple.com/lookup?id=6753895889&country=cn>) and the corresponding feature entry points. Interface labels may change with the version. Feature access is determined by the app’s current purchase screen.