AirDrop and local import

Send a comic to ManYue with AirDrop: confirm the received location before import

Send one authorized comic between Apple devices and verify AirDrop receipt, file location and ManYue import.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Send one authorized comic between Apple devices and verify AirDrop receipt, file location and ManYue import.

Fix sender and recipient

Prepare two nearby Apple devices: one with a small owned or authorized CBZ original, the other with ManYue installed. Record filename, size, edition and recognizable first and last pages; retain the original on the sending device. This uses system AirDrop first, then imports from the actual saved location, and does not assume ManYue appears in the receiving menu. For another recipient, confirm their consent and reading rights before sending; do not use private or unauthorized comics as practice. First check the recipient has enough free space for the sample and imported copy.

Check AirDrop discovery conditions

Using the current system interfaces, enable Wi-Fi, Bluetooth and AirDrop on both devices, keep them nearby and check recipient visibility. Apple documents that Contacts Only and time-limited everyone settings depend on system version and contacts; newer systems may request a code, so follow the actual prompt. Devices using the same Apple Account may accept automatically; do not assume automatic acceptance for every pair. Record the original receiving setting to restore it afterward.

Send only one file from the source

In Files or Finder on the sending device, select the verified CBZ and use system Share and AirDrop to choose the recipient. Check the name to avoid sending to another nearby device. If the recipient sees Accept or Decline, follow the actual prompt and decline unexpected requests. Wait for completion on each side rather than closing or switching networks immediately after tapping send. Some systems can continue over a network after devices leave nearby range; conditions and charges depend on actual settings, so do not promise an entirely network-free transfer.

Find the actual received location

Observe how the receiving device offers to save or open the item. The system may choose a location or ask how to open it depending on file type, apps and OS version. If Save to Files appears, select a folder you can find again and record its path. Apple says some received items may be in Files; that does not guarantee every CBZ goes to one fixed folder or automatically enters ManYue. If no location is shown, follow the actual entry and mark import untested if the item cannot be located.

Compare the received file with the source

Browse to the received location in Files and compare filename, size and folder. If the system added a suffix to a duplicate name, use time and the original to identify it rather than guessing edition from the number. Try any system preview or file information actually offered, but lack of preview does not by itself prove a CBZ is corrupt. Transfer completion, an entry in Files and readable content in ManYue are separate layers. If size is abnormal or failure is explicit, retain the original and recheck the transfer without deleting same-named files.

Select the received copy in ManYue

Open the local comic import entry actually visible in ManYue. Locate the received file in the system picker, select one item and wait for processing as prompted. If the system offered ManYue directly on receipt, follow only the option actually shown; do not infer all systems or files support it. Once a work appears on the shelf, check name and edition, then compare first, middle and last pages with the sending record. If only a cover is visible or processing continues, record that separately rather than treating transfer success as completed import.

Troubleshoot discovery by layer

If the recipient is absent from the sender list, first check proximity, Wi-Fi, Bluetooth, receiving options and visibility under the current OS. For Contacts Only, verify account and contact-card details. If a newer system requests a receiving code, enter it only after confirming the recipient and do not publish it in notes. If the target appears but transfer fails, record both devices’ messages, file size and time, then check connection and recipient storage. Avoid changing many settings at once, which obscures the cause. With time-limited receiving, check the window has not expired; the device owner can renew it using current prompts and restore the previous scope afterward. If AirDrop is absent on a managed device, system or organizational policy may apply: ask its administrator rather than bypassing restrictions. If network conditions cannot be met, preserve the source and use an existing local-file import path later.

Recheck the work and restore receiving settings

Leave the reader and reopen the target on the shelf. If practical after transfer and import finish, temporarily disconnect the network and recheck sampled first and last pages, then restore it. Record sending, received location, import and local reading separately as success, failure or untested; offline samples cover only those pages. Restore the prior AirDrop receiving scope as needed and confirm the sender original remains. Do not treat the received copy as the sole backup. This entry and its receiving conditions differ from browser-based Wi-Fi transfer, while content still needs verification.

Local comic basics; Browser-based Wi-Fi import.

Checked 20 November 2026: Apple lookup lists ManYue 2.0.6 and iOS / iPadOS 15.0 or later; local-file import appears in the App Store. See Apple’s AirDrop guide for discovery, receiving and location. No device, AirDrop or offline test is claimed.