ManYue: Read storage categories before deciding what occupies space

When a device reports low space, one total does not tell you what needs attention. ManYue 2.0.4 publicly adds storage-category statistics. This lesson first establishes what the readings mean and where data belongs, before deciding whether further action is needed. Use a small sample with an original copy throughout. Do not infer the purpose of data by deleting private directories, or treat the app statistics as a complete account of the device disk.

Fix the comparison time and sample

Pause new imports and downloads that you initiate. Wait for existing work to finish, or explicitly record the tasks still running. Prepare a six-page comic you created, recording its filename, format, file size and the location of the retained original. In an external note, create five fields: date, app version, before readings, after readings and tasks at the time. If the device is also updating the system or downloading in another app, record that context. Do not attribute every change in system free space to ManYue. These preparations fix observation conditions; they do not require disabling system services or terminating unfamiliar processes.

Copy the four category readings by their visible labels

Open the app-data area in Settings and use the labels actually visible in your installed version. Copy the readings for cache, local comic storage, other temporary files and app data storage. If calculation is in progress, wait for it to finish. If the value is Unknown, record Unknown rather than zero. The local source shows these categories and waiting states, but that is not a measurement of this device. Do not abbreviate all four labels to the ambiguous word cache. Do not add the system Documents and Data figure to these categories merely to produce a total: the two views may use different scopes and update times.

Import one known file and observe its category

After recording the first readings, import only the prepared comic. Confirm that its entry appears on the local shelf and that the first, middle and last pages open, then return to the same settings area. Look for an explainable change in local comic storage while retaining the changes in the other three categories. Do not require the increase to equal the original archive size exactly: extraction, covers and supporting data can change how it is stored. If import is still processing, record that state instead of declaring temporary growth to be abandoned data. A successful check explains entry identity, readable pages and category readings together; it is not a coincidental numerical match.

Read a small sample to distinguish regenerable material

Read several pages of that comic, then leave the reader and return to Settings. If available, open a few pages of a short remote sample you own while online, and record whether the cache reading changes. Without a remote sample, skip this part; an empty result cannot establish a failure. Reading caches reduce the cost of obtaining or processing content again, but that does not mean every page belongs to one identical category. In particular, downloaded or imported local comics are not disposable image-cache entries. Record the actual object and network state so that a later offline-opening problem can be related to these readings.

Identify active work within temporary files

The description of other temporary files includes pending downloads and imports. When this category grows, first check task names, states and start times in the task list. If a task is still active, do not delete its intermediate files through a file manager or repeatedly clear data to hurry it along. After completion, reopen Settings for another reading and compare task-state changes and category redistribution. If a task fails, preserve the visible error and sample details, then use the normal task-handling entry. This lesson provides no forced cleanup path that bypasses app state. Temporary describes a purpose; it does not establish that a file currently has no user.

Explain differences from system storage statistics

Record the application footprint shown in system Settings separately, with its own time. If the two views differ, first confirm the same device, time and app, then consider cache rebuilding, delayed system accounting and different category scopes. Do not label the difference hidden comics or a data leak without evidence, and do not promise that adding the app categories must exactly reproduce the system figure. For a useful report, include both sets of labels, complete readings, screenshot times and active tasks, rather than saying a few hundred megabytes are missing. Defer comparisons while a view is still calculating instead of forcing changing numbers into agreement.

Keep unknown states when checks do not resolve

If a reading does not change immediately after import, first confirm actual task completion, then leave and re-enter the settings area and wait for scanning. If a category remains Unknown or implausible, record which category is affected, whether the others look normal and whether the sample reads. Do not import the same file repeatedly to create a larger difference, or make reinstalling the app your first response. You may repeat the check once with a smaller self-made sample, changing only one condition. If the behaviour cannot be reproduced consistently, mark the conclusion unconfirmed. Unclear accounting and a damaged comic are different observations and need separate evidence.

Keep a record that supports the next decision

Keep at least three rounds in the final note: before the operation, after the single import and after limited reading. Attach completion state and reading time to each round. State which data has an original, which can be obtained again and which is still used by a task. Defer deletion decisions for unexplained data. Leave the app and return, confirming that the sample entry remains and the same pages open, before moving on to storage budgeting or cache settings. Completion means you can explain the likely category and uncertainty of every observed change, rather than reducing every category to its minimum.

Related guides and sources

ManYue download storage budget: estimate space for a week of comics; ManYue downloads: manage the queue, retry failures and verify local copies.

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.