Moving a Shadowrocket subscription to Android or Windows without copying bad fields

Porting a Shadowrocket subscription: the URL usually travels; the fields might not. Add the sub on the new OS, update, connect one node you already trust on iOS. If that fails, diff protocol parameters—do not dump the whole iOS profile and declare the PC broken.

This site is iOS-first. Other clients are whatever the download page lists. Fake rocket icons are common.

Smallest experiment

1. Subscribe only, no remote rules.
2. The same node that was healthy on iPhone.
3. TCP/compatible on office Wi-Fi.
4. Rules after a page loads.

VMess path, host, TLS, and transport names drift across apps. Fill from provider docs. Office networks drop UDP more than LTE. Windows plus PAC is a stacked proxy again. DNS: DoH. Fetch failures: update fail. FAQ, guides.

Field questions tied to this guide

• iOS fine, Windows all timeouts. UDP dropped on the office net, or TLS/path fields diverged. Try a compatible/TCP mode, then diff that one node.
• Can I paste the iOS rule file elsewhere? Syntax may differ. Get one node green first.
• Is every 'rocket' icon on Android the same app? No. Trust the developer and the download page.
• Does the iOS purchase cover Windows? No. Buy or install the desktop client separately; the subscription is yours.

Change one control, then retest

While working through “Moving a Shadowrocket subscription to Android or Windows without copying bad fields”, write the download-page version, mode, protocol, and node name on the first line of a note. After each toggle, run one check only: 1.1.1.1/help or the exact page that failed. Changing Kill Switch, split rules, and nodes together makes the next failure un-debuggable. Get Shadowrocket packages only from the download page; permissions and device limits live in the FAQ and guides.

On office or hotel networks, finish captive portals and clear leftover PAC entries before you decide this article’s failure mode applies. A cellular A/B exposes router DNS and parental filters quickly. Avoid hammering login on a second device during the test so session kickouts are not mistaken for radio drops.

Pin the combination that works—SSID, node, protocol—and reuse it on that network instead of starting from Auto every time. Keeping slug rocket-android-desktop-port as your note title makes the write-up searchable later.

When to stop and change layers

After five identical failures, stop. Recheck the documented build, confirm a single tunnel client, ensure Kill Switch was not blocking a portal, and verify the browser is not Direct in a split list. Stopping is how you escape the wrong layer.

When you ask for help, include time, SSID, mode, protocol, node names, and steps already tried. After recovery, verify egress in a clean browser so cache does not fake success, then write the split list or favorites back into your notes before the next reinstall.

Extra pass for “Moving a Shadowrocket subscription to Android or Windows without copying bad fields”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Moving a Shadowrocket subscription to Android or Windows without copying bad fields”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Moving a Shadowrocket subscription to Android or Windows without copying bad fields”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Moving a Shadowrocket subscription to Android or Windows without copying bad fields”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Moving a Shadowrocket subscription to Android or Windows without copying bad fields”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.