Wi-Fi import connection troubleshooting

ManYue Wi-Fi import page will not open: check the current session and local-network permission

Check the device’s current session address, local reachability, system permission and pairing separately, then verify one small comic.

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

Check the device’s current session address, local reachability, system permission and pairing separately, then verify one small comic.

Fix one actual session first

Prepare the iPhone or iPad running ManYue, one computer and a small comic you are authorized to use. Retain the computer original. This exercise diagnoses access to the device’s actual Wi-Fi import page before uploading a whole collection. Record device identities, current network, app version and time; redact pairing codes, full private addresses and credentials from shared notes. If this installed version has no identifiable Wi-Fi import entry, mark it unconfirmed and use an existing local-file import route rather than inventing a hidden button.

Read the currently displayed address

Enter the actually visible Wi-Fi import flow in the installed version, observe whether its service is running and read the full address displayed for this session. Do not reuse yesterday’s screenshot or browser bookmark: address, port or session information may change when the device rejoins a network. Enter it as an address in the computer browser, retaining the protocol, host and port actually shown. An example is not your session’s value. If pairing is requested, follow the current prompt and do not publish an old pairing code.

Distinguish internet access from local reachability

Check each device’s current network. Internet access on both devices, or even matching Wi-Fi names, does not alone prove that the computer can reach the local page offered by the mobile device. Guest networks, client isolation or management rules may affect reachability; the maintainer must confirm the actual environment. If an authorized mutually reachable home network is already available, you may use it while holding other conditions fixed, create a fresh session and test its newly displayed address. Without network-management permission, record the limit; do not expose a public service, disable network protections or guess router settings.

Check the actual local-network permission

Apple documents Settings → Privacy & Security → Local Network for viewing or changing access for listed apps on iOS and iPadOS. If ManYue appears in the current list, record its state. The user decides whether to allow it and can restore their original preference after a change. If the app is absent or system wording differs, record that the state could not be confirmed rather than assuming a switch exists. After any permission change, return to the app and recheck the current session and page; a switch state alone is not a successful connection. Permission is one condition; a page can still fail because of service state, address or network.

Separate an unreachable page from pairing failure

While the mobile service is actually running, open its current address on the computer. Record whether the browser could not load the page, a page appeared but asked for pairing, or file selection failed only after pairing; each stage calls for different next checks. For no page, first inspect session address and local network. For a visible page with pairing failure, inspect current pairing information and the actual message; do not repeatedly enter an old code or share it publicly. A visible page does not mean any file has uploaded; mark unstarted steps untested.

Recheck the session after app or network changes

If the phone switched apps, locked or rejoined Wi-Fi, or the computer changed networks, return to the ManYue import interface and observe actual service state and currently displayed address. Foreground and background behavior depends on installed version and system state; this lesson promises neither continued service nor stopping. If a new session is needed, start it through the current interface and use its displayed address and pairing prompt. Refreshing an old saved computer page does not establish that the new service is broken. Change one condition at a time and record when.

Verify one small file only after the page works

Only once the page works and any pairing it requests has been completed, select the owned small comic and submit it through the page’s available flow. Observe browser transfer result, device processing result and the actual shelf entry separately. Open first, middle and last pages and compare identity with the computer original; 100% upload alone does not establish parsing and import. If the page works but upload fails, record file size, storage, message and destination separately instead of continuing to call it an unreachable address. Earlier connection findings remain useful even if this step cannot be performed.

End the service and retain a reproducible record

After finishing or pausing, end the temporary import service through the current interface, confirm the computer original remains and restore settings you personally changed. Record devices and app version, service state, whether the address matched the current display, network scope, whether local-network permission was confirmable, page or pairing outcome, and actual upload and reading results. Mark unseen states unknown and unperformed tests untested. One home-network success does not guarantee access on a school, hotel, guest network or future session, and does not establish a bidirectional comic backup.

Wi-Fi import basics; Wi-Fi folder preview checks.

Checked 20 November 2026: Apple lookup lists ManYue 2.0.6 and iOS / iPadOS 15.0 or later; local comic capabilities are described by the App Store. System permission reference: Apple local-network privacy. Actual app entries depend on the installed version. No device, network or transfer test is claimed.