Verify the product before confirming payment
The name and icon in search results are only a starting point. Open the product page and verify the app name, Shadowrocket, the developer, Shadow Launch Technology Limited, and the App ID 932747118 in the product link. The official icon matches the one shown here, but color or a rocket shape alone is not enough to identify the app. Before confirming your purchase, check the developer and product details again to avoid mistaking a similarly named app for the right one.
App Store visibility depends on the storefront associated with your Apple ID. If you cannot find the product, check which App Store storefront you are browsing and whether the product page opens. The currency, purchase status, and compatibility shown on the page also depend on your current account. Do not assume a reference price shown in US dollars online is the amount you will pay locally. Confirm availability for purchase and installation in the App Store on your device.
What the One-Time Purchase Covers
Shadowrocket is a paid, closed-source commercial app available as a one-time purchase. The US storefront reference price is $2.99; other storefronts show local currency, and the final amount is shown on the purchase confirmation screen. The purchase gives you the right to use the client; it is not a monthly network service. Before buying, understand the app price and the terms of any service you already use as separate items.
A client purchase is not a network plan. This guide does not provide, sell, or recommend servers or subscriptions; it explains how to import and use your own configuration. If no server entries appear after opening the app, that does not mean the purchase failed. You may still need to import your own subscription or enter details from a server you already have using Add Server. Check the original service details and test results to see whether a subscription can update or a server is working; purchase status alone cannot tell you.
Using and Restoring a Purchase on Two Devices
The purchase association between iPhone and iPad depends on the App Store purchase status for the same Apple ID and the applicable purchase terms. To use Shadowrocket on another device, check the store account first, then look for the app on its product page or in your purchased items. Do not rely on the account name used for other device services to determine which account made the App Store purchase; the purchase record should match the Apple ID currently signed in to the App Store. Refer to the App Store listing for compatibility, system requirements, and whether the purchase is universal.
When replacing a device or reinstalling the app, find it in your App Store purchased items and check that you are using the original purchasing account. Restoring the app and restoring its configuration are separate steps: after reinstalling, check your server details, Config file, and device authorization. If you use iCloud sync, wait for it to finish and verify the result before importing again, to avoid editing data before confirming what synced. For Family Sharing, check the App Store listing and your account for the sharing options actually available.
Updates, Configuration, and Restorable Copies
App updates are delivered through the App Store; check the store's release notes for details. If interface elements move after an update, look for them by their labels, such as Home, Config, and Settings, rather than relying on fixed coordinates in a screenshot. The homepage does not list fixed version numbers or update dates. Check the App Store listing for system requirements too, and do not treat older guide text as confirmation that the app is compatible with your current device.
Before editing a configuration, keep a restorable copy and note the current Global Routing mode, server selection, and key settings. Importing a new Config may change rule order, DNS behavior, or fallback handling; a successful import does not mean the previous behavior will remain unchanged. Review General and Rule first, then test under comparable conditions. If something goes wrong, restore a known-working copy instead of piling on uncertain changes.
Sensitive Information in Imports and Logs
Authentication parameters in subscription links, server passwords, and access logs may contain private information. Before asking for troubleshooting help or sharing a screenshot, check full URLs, authentication fields, and target domains, and remove anything you should not share publicly. The example.com and token=xxxx values in the guide illustrate format only; they are not real server details. When saving a configuration copy, check whether it contains account information and avoid putting files with authentication details in public locations.
Troubleshooting requires reproducible conditions, not full disclosure of your details. You can usually start by noting the network, Global Routing mode, rule keyword, where the error occurred, and which tests you have completed. Keep specific server authentication details in your own configuration. If only one website is affected, check which rule matches its domain. If all destinations fail, check the server, system authorization, and DNS. Isolating the issue layer by layer is more useful than changing several settings at once.