04 / PRODUCT VERIFICATION
Verify the app using these three details
Shadowrocket is a closed-source commercial app. Verify it by checking the product page, not just the name in search results. Compare the developer, official icon, and app ID; all three should match.
01 / DEVELOPER
Developer
Check for Shadow Launch Technology Limited on the App Store product page. Similar names in search results are no substitute for checking the developer. Open the product details and confirm the name there rather than relying on an abbreviation or search recommendation.
02 / ARTWORK
Official app icon
Compare the icon with the official one shown on this site: a rocket outlined in blue and purple on a white background. The icon can help identify the app, but it does not prove its identity on its own; also check the developer and app ID.
03 / APP ID
932747118
The official product page URL contains id932747118. Open the product page from the verification guide and check this identifier. If a similar-looking result has a different app ID, it is not the same app.
App purchase ≠ connection service
The one-time purchase covers the app only; it does not include servers, subscriptions, or connection services. You need your own server details or subscription to import into the app. Server validity, authentication, and availability are managed by the original service and are separate from your App Store purchase. This guide does not provide, sell, or recommend servers or subscriptions.
The US storefront reference price is $2.99; other storefronts show local currency, and the amount on the purchase confirmation screen is final. If the price, currency, or purchase button differs, check your current account and storefront instead of assuming the transaction outcome from the reference shown here. Keep your purchase record to help restore the app or investigate a possible duplicate purchase.
Restore purchases and configurations separately
Sign in with the same purchase account and look for Shadowrocket in the App Store purchase history on your iPhone or iPad. Purchase eligibility is as listed on the App Store page. After restoring the app, check whether the device has the server details and configuration you need. A purchase record confirms the purchase; it does not mean every setting from an old device has transferred or that the old server is still valid.
Back up your current configuration before changing devices, and check which items the sync feature actually covers. On a new device, follow the system prompt to confirm permissions the first time you connect, then select the current server and Config. If a file appears but the connection does not work, check local permissions, the current selection, and the original server status separately. Restoring a purchase does not replace connection testing.
Manage app updates in the App Store
Check the App Store for update history, compatibility, and current product details. Keep a restorable copy of your configuration before updating. Afterward, check the server selection in Home, Global Routing, and Config, then test your usual destinations. The interface may change; this guide uses English interface labels to help locate features and does not assume a button will always remain in the same place.
If you cannot install or update the app on your device, first check the App Store compatibility notice and available storage, then verify the system requirements. Keep configuration import issues separate from app availability: for the former, check the file contents and format; for the latter, check the App Store and device messages. Troubleshooting each issue at the right level avoids unnecessary repeated steps.
Keep the original settings, then make one change at a time
DNS, Rule, On Demand, and protocol fields affect different parts of the connection. Record current values and keep the original Config before making changes. Change one condition at a time, then retest using the same destination and network. If the result gets worse, undo the last change before trying another. Changing several things at once makes results hard to compare and can lead to removing settings that were working.
When reviewing Data, note the time period and reporting scope; when checking latency, note the Test Method. Traffic statistics show usage, while latency tests offer a clue about that particular test. Neither replaces visiting the destination yourself. To understand a field, look up its term in the quick reference, then read the relevant section of the system guide instead of guessing at an English option from a similar-sounding term.