Sandbox tester account will not sign in or does not show on the device
Sandbox account does not appear in the App Store section in SettingsShort answer
A sandbox tester fails when its email was already an Apple Account, when the app is not a development-signed build, when Developer Mode is off, or when the Paid Apps Agreement is not Active. Create a fresh tester with a new email, sign in using the Sandbox option, and run a development build.
Fix it fast
1Find out which cause you have
Check the agreement first, because it blocks everything else: App Store Connect > Business > Agreements, Paid Apps row must read Active.
# No command: App Store Connect > Business > Agreements > Paid Apps2Match what you see, then jump to its fix
- 1
Errors during the purchase sheet even though the password is rightThe tester email was already an Apple AccountFix - 2
The sandbox sign-in never appears, or the app talks to the real App StoreThe build is not development-signed, or Developer Mode is offFix - 3
Products come back empty or purchases fail for a correctly signed testerThe Paid Apps Agreement is not Active, or product data is still syncingFix
- 1
What does the error look like?
Sandbox account does not appear in the App Store section in SettingsCannot sign in with the sandbox tester during an In-App Purchase
Cause 1 of 3
The tester email was already an Apple Account
1Check
Apple says the email for a sandbox account must not already be registered as an Apple Account, and must not have been used to buy iTunes or App Store content. Using one causes errors during testing.
# App Store Connect > Users and Access > Sandbox > Testers: open the tester and read its email2Fix
Create a new tester with a dedicated email nobody has used for an Apple Account. A plus-sign subaddress of a sandbox-only address is allowed if your mail provider supports it. Name, email and password cannot be edited after creation, so make a new tester instead of fixing the old one.
# Users and Access > Sandbox > Testers > + > name, new email, password, country or region > Create3Verify
Sign in with the new tester when the purchase sheet asks.
# Trigger a purchase in the app and sign in as the sandbox testerConfirmed by developer.apple.com
Cause 2 of 3
The build is not development-signed, or Developer Mode is off
1Check
Apple says to sign in with sandbox accounts on devices running a development-signed version of your app, and to enable Developer Mode on each test device.
# Developer Mode must be enabled on the test device (see Apple: Enabling Developer Mode on a device)2Fix
Run the app from Xcode onto the device with a development profile, after turning Developer Mode on. Use the Sandbox sign-in option in Settings, not your main Apple Account settings. For In-App Purchases you do not need to sign out of your personal Apple Account.
# Xcode: select the device, Product > Run (Debug configuration)3Verify
The purchase completes without a real charge.
# Complete a test purchase and check the transaction in your appConfirmed by developer.apple.com
Cause 3 of 3
The Paid Apps Agreement is not Active, or product data is still syncing
1Check
Apple states the agreement must be Active to test In-App Purchases in the sandbox, and that changes to product metadata can take up to 1 hour to appear in the sandbox.
# Business > Agreements > Paid Apps: status; note when you last edited the product2Fix
Get the agreement to Active (Account Holder, with banking and tax complete), then wait up to an hour after product edits before retesting.
# Business > Agreements > Paid Apps > View and Agree to Terms (Account Holder)3Verify
Products load in the app and the sandbox purchase completes.
# Retry the purchase in the development buildConfirmed by developer.apple.com
How do I stop it coming back?
- Use a dedicated mailbox with subaddresses for testers and never reuse a personal Apple Account email.
- For quick local tests that need no App Store servers, use StoreKit Testing in Xcode.
- Wait up to an hour after changing product metadata before blaming the code.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
Can't find or sign the Paid Applications Agreement in App Store Connect
Paid Apps agreement status is not Active
The Paid Apps Agreement is under Business, then the Agreements tab, in the Paid Apps row.
3 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fix