![]() Your device may repeatedly ask you to sign in to your sandbox account when attempting to test a purchase. If you’re testing on iOS 11 or earlier, you’ll need to sign out of your production App Store account, then sign in with a test account when prompted within the app.) (The Sandbox Account section of the Settings app was introduced in iOS 12. When in doubt, create a fresh sandbox account and retest. If you accidentally use a sandbox account on the production App Store, that account will no longer work in the sandbox. Here, you can log in and out of different sandbox accounts for testing. Once you have logged in to a sandbox account using this method, you can then go to the Settings app, tap iTunes & App Store, then scroll to the bottom to the Sandbox Account section. To sign in with a new sandbox account for the first time, you must attempt to make a purchase in a developer build of your app. Apple has good documentation on this - hopefully it will stay up to date! IOS testing in the developer sandbox requires a sandbox account. To prevent apps from being distributed widely outside the App Store, Apple limits device provisioning to 100 per device type (iPhone, iPad, Apple Watch, Apple TV, and Mac) for a total of 500 devices. Developers often use this to quickly test on-device during the development process, but you can also provision devices and distribute developer builds to QA and other internal testers without having to go through TestFlight and their beta app review. To test in the developer sandbox, the app has to be built as a developer build in Xcode. Make sure you understand its quirks and limitations during development to save time when you move on to production testing. The developer sandbox is your first line of defence. Each one of these environments behaves a little differently, and ideally you should test in all three before releasing your app. There are three different testing environments you can use to test your iOS app at different stages of the development and release cycle: sandbox (developer builds), TestFlight (the production sandbox), and production (the App Store). Looking for a guide to Android? Check out our Android subscription testing guide > iOS testing environments We’ll update this post over time as Apple makes changes to subscriptions and we figure out better ways to test. So we put together this guide to fill in some of the cracks. Apple’s subscription-related documentation is… shall we say… lacking, and Apple doesn’t provide many testing resources. Testing App Store subscriptions is extremely important, but it’s also hard to do well.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |