Check your account region if the app is not listed
If you cannot find the app in the iPhone / iPad App Store, first check the Apple Account used for “Media & Purchases” and its storefront region, rather than relying on the device language or your physical location. The app is not available in the mainland China storefront, and changing the device language will not switch storefronts automatically. Check “Country/Region” in account settings, then review age-rating restrictions, sign-in status and payment requirements.
If you need to change your storefront region, review the account requirements first and address any factors that may affect the change, such as account balance, existing subscriptions or Family Sharing. Do not confuse “not found in search” with “device incompatible”: for the former, check the storefront and account; for the latter, follow the system requirements shown on the App Store page. The app verification guide explains each case.
Purchases, device changes and restoring purchases
iPhone / iPad: $2.99 one-time via the App Store, shared by both devices; Mac, Windows, Android and Linux versions are free. Before changing devices or reinstalling, confirm the original purchasing account. On the new device, find Shadowrocket under “Purchased” in the App Store and download it again. If the page still shows a purchase button, check that you are using the same account, that the record is not hidden and that the current storefront displays the app.
Downloading the app again and restoring configuration are separate steps. A purchase record does not restore server passwords, subscription addresses or local rules automatically. Save your own original details before moving devices. For Family Sharing, refer to the sharing terms shown on the product page and in Family settings; availability is not necessarily the same for every account or storefront.
App purchase ≠ service plan
Getting the app only provides the client; it does not create a connectable server. This site does not provide, sell or recommend nodes or subscriptions. All import instructions assume that you already have your own subscription or server details. For expired subscriptions, authentication errors or device limits, first check the account and original parameters for your existing service.
So, a successful App Store purchase with no server entry in Home does not mean the purchase failed. Prepare valid details, then add or import them using the guide. If an existing entry cannot connect, check the protocol, address, port, authentication and network path. Repeatedly purchasing the client will not fix a server-side error.
Follow a consistent order for the first connection
In Home, first confirm that an entry appears in the SERVER group, select it and run Connectivity Test. Next, check Global Routing: for everyday rule routing, use Config and confirm that the intended file is selected in Config. After responding to the system's connection permission prompt, visit a specific destination in a browser and check the result rather than relying only on the connection toggle.
If the test succeeds but an app fails, keep the working server and continue by checking the rule matched by that destination, DNS resolution and the app's own network settings. Config, Proxy and Direct can help narrow down the issue, but note the result after switching modes and restore the intended setting. Changing several parameters at once makes the cause harder to identify.
Update the app and subscription separately
App Store manages client updates for iPhone / iPad. Mac, Windows, Android and Linux users can get the corresponding updated package from this site's download page. Before updating, save your current configuration and necessary authentication details. Afterward, check the selected server and rules file, then test the connection. Version details shown on the page are read dynamically from the download manifest; do not use an old article's version as a selection guide.
A subscription update fetches the server details provided by the subscription; a configuration update may change rules or DNS. Neither is an app update. If behavior changes after an update, first identify which layer changed, then check for removed entries, modified protocol fields or a different rule order. This helps preserve what still works and reduces repeated setup.
Keep diagnostic details to investigate DNS issues
If a domain cannot be accessed, first distinguish “domain could not be resolved” from “address resolved but connection failed.” Note the failed destination, network type, selected entry and Global Routing, then review Diagnostics and relevant logs. Save the original value before changing DNS and retest the same destination. Changing several DNS addresses at once usually does not reveal which one took effect.
Traffic in Data indicates that data is being transferred; it does not mean every request has completed. Connectivity Test results also depend on the test method and destination. Before sharing diagnostic details, hide full subscription addresses, passwords and personal browsing records. example.com in the rule examples is for syntax illustration only.