Shadowrocket FAQ

First check the purchase account and storefront currently used by the App Store, then see whether the app is available in that storefront. Your device’s language or region setting does not determine the storefront linked to your purchase account. In system Settings, go to Apple Account, Media & Purchases, then View Account and check Country/Region; exact menu names may vary. Before changing regions, review Apple’s listed requirements for balances, subscriptions, and payment methods. Don’t change your region just to affect search results. Check the App Store listing for system requirements. Not finding the app in search does not mean your purchase history is gone.

Check the product name, Shadowrocket, the developer, Shadow Launch Technology Limited, the official icon, and app ID 932747118. You can identify the app ID from id932747118 in the product page URL. The icon should match the official one shown in this site’s header. Don’t rely only on search ranking or a similar name. After opening the App Store from this site’s app page, verify the product details, account, and local-currency price before confirming your purchase. Refer to the product page for the current version details, compatibility, and purchase terms. A similar name is no substitute for checking the developer and app ID.

You can usually redownload Shadowrocket from your App Store purchase history using the same Apple ID you used to buy it, without paying again. First check which account is used for Media & Purchases, then look for the app in your App Store account’s purchase history; menu names may differ by system version. If a price button appears, pause before confirming payment and check your purchase history, hidden purchases, and storefront region. Redownloading the app and restoring its data are separate things. Check whether your subscriptions, server details, and Config are still available based on your backups. Restoring a purchase does not automatically restore all settings.

A one-time app purchase is not a service plan. It gives you the right to use the Shadowrocket app; connecting still requires your own existing subscription or server details. The app purchase and any related service have separate terms and expiry dates. Shadowrocket is a closed-source commercial app. The US storefront lists it at $2.99; the actual price, taxes, and local-currency prices in other storefronts are shown on the App Store purchase confirmation screen. Check the product page for current details on Family Sharing, supported devices, and purchase terms. This site does not provide, sell, or recommend servers or subscriptions. An app purchase record does not indicate whether an existing service is active.

Shadowrocket is available for iPhone and iPad; check the App Store listing for system requirements. On iPad, sign in with the same Apple ID used for the original purchase, find Shadowrocket in your purchase history, and download it as prompted by the store. You usually do not need to buy the same app again; refer to the product page for purchase terms. The iPad layout may vary with screen size. Use interface labels such as Home, Config, and Settings to find controls rather than relying on coordinates from a particular screenshot. After installation, check your existing subscription or server details and confirm system authorization separately the first time you connect. Don’t assume settings have synced from another device.

This is the system authorization step for a VPN configuration, not a purchase confirmation, and it does not fill in server details for you. Confirm that the prompt was triggered by a connection attempt you just started in Shadowrocket, read the system notice, then authorize with your passcode or biometrics as required by your device. Return to the app, check the selected entry and Global Routing, then try connecting. If you dismissed the prompt, start another connection attempt and check the system response. If your device is managed by an organization or has restrictions, review the relevant policies first. Don’t delete unrelated configurations just to complete authorization, and don’t assume that a VPN icon means your connection is working.

Use the labels shown in the app: Home displays connection status and server entries; Add Server adds details; Subscribe imports an existing subscription; Config manages configuration files; and Settings contains app settings. Under Global Routing, the options are Config, Proxy, and Direct. Tutorials retain these English labels. To change the app’s display language, check whether your system offers a language setting for it; available options depend on your device. Menus may be arranged differently across system and app versions, so check each item’s name and purpose rather than relying on button color, row number, or screenshot position.

First distinguish incomplete system authorization from a connection that starts and then drops. Check that a valid entry is selected on Home, see whether a VPN authorization prompt appears, and note the exact system or app error. If the switch turns off as soon as you enable it, check in order that your existing server details are complete, your network is working, and there are no conflicts with another VPN connection or device management restrictions. Keep your current Config and essential details, then make changes one at a time; don’t start by deleting the app. Also check whether On Demand is triggering connections based on its conditions. Identify the failing step before deciding whether the issue is system authorization, configuration content, or the remote service.

First make sure the subscription link from your own service provider is complete and that no spaces, line breaks, or explanatory text were added when you copied it. Confirm that it should be imported using Subscribe, rather than entered as a single server address. Then check whether your current network can reach the link, whether the subscription is still active, and whether its response is in a format supported by Shadowrocket. Note the status or error shown during import; avoid changing several fields and retrying repeatedly. Subscription URLs may contain access credentials, so don’t share the full link while troubleshooting. If you need to contact your provider, describe the error and use their existing support channel. This site cannot receive or inspect private subscriptions.

If the list is empty, check the subscription response before reinstalling the app. Verify the group you’re viewing, whether the subscription update succeeded, and whether the result reports a parsing error. A reachable link does not guarantee that it returns importable entries; it may return a login page, an error message, or no content. If you had entries before, keep your existing configuration rather than deleting and rebuilding it right away. Ask your provider to confirm the subscription status, output format, and whether it still contains usable entries. A successful app purchase and valid subscription content are unrelated. Changing the Global Routing mode cannot fix an empty response from the service.

Update an existing Subscribe item when your provider changes server details, an entry stops working, or you need to sync subscription content. The exact controls depend on the app version. An update rereads the link; it does not extend the related service or automatically select the best entry for your current network. Before updating, note the entry in use and any essential custom settings. Afterward, check the groups, changed entries, current selection, and any error messages. If the update fails, check your network and subscription status rather than retrying repeatedly. Clearing the list should not be a routine step before every update.

Subscribe reads server entries from an existing subscription. To add a single server, use Add Server and enter the address, port, and authentication fields required by its protocol. Config manages rules, policies, and related settings; these are different types of content. Before importing, identify what you have and check its format and purpose. A Config containing only rules may not include a server you can connect to, and a server entry alone does not provide the rules you need. Keep the original file before replacing a Config. After importing, check both the selected entry and Global Routing; a successful import does not mean the setup is complete.

Choose Config when you want rules to determine where requests go. Choose Proxy to test a connection using the current proxy policy. Choose Direct to check your local network without the proxy route. Config depends on the active configuration file and rule order; it does not mean every request uses the proxy. Direct cannot verify whether a remote server is working. For troubleshooting, keep the same test destination, change one mode at a time, compare the results, and then restore your original setting. If Config fails but other modes produce different results, check the matching rules and policies. A page loading once does not prove that all rules are correct.

A connected status means a connection has been established; it doesn’t guarantee that every request will succeed. Disconnect and check whether your local network can reach a destination that normally works, then reconnect and check the selected entry, Global Routing, and service status. When using tools such as Connectivity Test, distinguish the test result from what happens when you load an actual webpage. One successful test does not prove that DNS, rules, and the destination service are all working. If only some destinations fail, check their rules and DNS. If everything fails, start with your local network, selected entry, and authentication details. Change one variable at a time and keep the error message; changing the network and configuration together makes the cause harder to identify.

Note the affected domain, when the failure occurred, and which Config was active. Then review available request logs to see which rule matched and which policy was used. Rules generally match from top to bottom: an earlier DOMAIN-SUFFIX, IP-CIDR, or REJECT rule may prevent a later intended rule from taking effect. FINAL handles requests that did not match an earlier rule. Check DNS resolution separately from policy matching: first confirm whether the domain resolves, then check where the request is routed. Keep the original configuration and change only the relevant rule or DNS setting before retesting. Replacing the entire Config and all DNS settings at once makes the cause difficult to identify.

Check the system battery report for the time period, foreground and background activity, and actual network use. Don’t judge an issue by the app’s battery percentage alone. Continuous traffic, frequent reconnects, network changes, and diagnostic logging can all affect battery use. On Demand triggers connections based on configured conditions; it isn’t a fixed battery-saving switch. Poorly chosen conditions may still cause repeated connections. Note your current settings, then compare always-on and on-demand connections under similar usage conditions. Check for unnecessary continuous tests or repeated reconnects. After making changes, verify that essential requests still work; reduced background activity alone does not prove that a setting is correct.