Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

Why I can't sign into App Store or TestFlight with my Apple ID?

You usually can't sign into the App Store or TestFlight with your Apple ID because of a two-factor authentication code you missed, a wrong password or the wrong Apple Account, or an Apple server outage, and not because the apps are broken. TestFlight adds its own reasons: you need a valid invite or redeem code, the build may have expired after 90 days, the tester limit may be full, or you may be signed into a different Apple Account than the one invited. Note that Apple renamed "Apple ID" to "Apple Account" in late 2024, so you may see either term while the credentials work exactly the same.

App Store vs TestFlight - Where the Problem Comes From

The App Store and TestFlight both authenticate with the same Apple Account, so most sign-in failures are shared. TestFlight layers extra, beta-specific blockers on top because it serves invite-only builds. This table shows which cause hits which app.

Cause	App Store	TestFlight
Wrong Apple Account or password	Yes	Yes
Two-factor code missing or expired	Yes	Yes
Account locked, disabled, or email unverified	Yes	Yes
Wrong device date and time	Yes	Yes
VPN, proxy, or network blocking Apple	Yes	Yes
Apple server outage	Yes	Yes
Region mismatch or payment/agreement pending	Yes	Indirect
Media & Purchases turned off	Yes	Yes
Restrictions, Screen Time, or MDM block	Yes	Yes
Missing invite or redeem code	No	Yes
Build expired after 90 days	No	Yes
Tester limit reached	No	Yes
Signed into a different Apple Account than invited	No	Yes

Apple Account Credentials and Two-Factor Authentication

The most common reason a sign-in fails is a problem with the credentials or the verification step that follows them.

Wrong Apple Account or password: Confirm you are typing the full Apple Account email, not a shortened username, and that Caps Lock or autocorrect has not altered the password. After several failed attempts Apple temporarily locks the account.
Missing two-factor code: Apple sends a six-digit verification code to a trusted device whenever you sign in on a new device or session. If you never receive it, request a new code, and make sure a trusted phone number is reachable to receive it by SMS.
Expired or reused code: Each code is valid for a short window and only once. Entering an old code, or reusing one you already submitted, makes the sign-in fail; always type the newest code shown.
On-screen Continue swallows your entry: On remote or streamed iOS devices the on-screen keyboard can overlay the Continue button, so the tap never registers. Use the host keyboard's Enter key to submit the Apple Account and password instead of tapping Continue.

Account, Region, and Device-State Problems

If the credentials are correct, the block is often the state of the account or the device rather than the sign-in form itself.

Account locked or disabled: A message that your Apple Account is locked or disabled for security reasons means you must verify your identity at iforgot.apple.com and reset the password before sign-in works again.
Unverified email: A newly created Apple Account whose email was never confirmed cannot sign in. Open the verification message Apple emailed you and confirm the address first.
Region or country mismatch: The App Store serves the country set on your Apple Account. A payment method or billing address from another country, or a store that does not offer the app you want, can block downloads even after a successful sign-in.
Payment or agreement pending: If a billing problem or an unaccepted Apple media agreement is outstanding, the App Store keeps prompting and refuses to complete sign-in until you update payment details in Settings.
Wrong device date and time: An incorrect clock breaks the certificate checks Apple's servers rely on, so authentication silently fails. Set Date & Time to update automatically.
Restrictions, Screen Time, or MDM: Screen Time, under Content & Privacy Restrictions, can disable account changes and the App Store, and a supervised or MDM-managed device can block installs, TestFlight, and sign-in outright.
Media & Purchases turned off: Open Settings, tap your name, choose Media & Purchases, and turn it on. This re-enables App Store and TestFlight purchases when the section is disabled.

Network, VPN, Proxy, and Apple Outages

VPN or proxy interference: A corporate proxy or VPN can route or block Apple's authentication endpoints, producing a generic "could not sign in" error. Turn off the VPN, switch off any proxy, and retry on a normal connection.
Firewall or restricted Wi-Fi: Guest networks and firewalls that block Apple traffic stop sign-in. Move to a standard network or mobile data to confirm the network is the cause.
Apple server outage: When the App Store, App Store Connect, or TestFlight is down, valid credentials still fail. Check Apple's System Status and Developer System Status pages before troubleshooting your own device.
Outdated iOS: A very old iOS version can fail newer Apple Account authentication or TLS requirements. Update the device under Settings > General > Software Update and try again.

TestFlight-Specific Reasons You Can't Sign In or See a Build

TestFlight can sign in fine and still show nothing to test, which feels like a sign-in failure. These are the beta-only causes.

No invite or redeem code: TestFlight is invite-only. You need a public link from the developer, or an emailed invitation or redeem code, tied to the Apple Account you sign in with. Without one there is no app to open.
Signed into the wrong Apple Account: The App Store and TestFlight can each hold a different account. If the invite went to one Apple Account but TestFlight is signed into another, the build never appears, so confirm both apps use the invited account.
Build expired after 90 days: A TestFlight build expires 90 days after it is uploaded to App Store Connect. Once expired it cannot be opened, reinstalled, or reactivated, and the developer must upload a new build.
Tester limit reached: An app allows up to 100 internal and 10,000 external testers. If the external slots are full, your invitation cannot be accepted until the developer frees space.
App no longer available: A developer can stop testing, remove a build, or pull the beta. When that happens the app disappears from your TestFlight list even though your account is fine.

How to Fix App Store and TestFlight Sign-In

Work through these steps in order; most sign-in problems clear within the first few.

Check Apple's System Status page first. If the App Store or TestFlight shows an outage, wait it out rather than changing settings.
Confirm the device clock by setting Date & Time to update automatically, and disable any VPN or proxy.
Open the App Store, tap the user icon in the top-right corner, and enter your Apple Account and password. On a remote device, submit with the host keyboard's Enter key, not the on-screen Continue.
Enter the latest six-digit verification code from your trusted device to complete two-factor authentication.
If sign-in is rejected, go to Settings, tap your name, open Media & Purchases, and turn it on; if the account is locked, unlock it at iforgot.apple.com.
For TestFlight, open the app and tap Continue, then make sure you are signed in with the same Apple Account that received the invite or redeem code.
If TestFlight shows no build, ask the developer to confirm the build has not expired, that you are within the tester limit, and that the beta is still active.

If you keep hitting account or device limits during QA, you can sign into the App Store and TestFlight and run beta builds on real iPhones and iPads in the cloud with Real Device Cloud, which avoids tying every test to a single physical device.

Frequently Asked Questions

Is Apple ID the same as Apple Account?

Yes. Apple renamed Apple ID to Apple Account starting with iOS 18, iPadOS 18, and macOS Sequoia in late 2024. It is the same login and the same credentials, just a new name. Older iOS versions and many third-party screens still say Apple ID, so you may see both terms when signing into the App Store or TestFlight.

Why does the App Store say my Apple Account is correct but still won't sign in?

When the credentials are right but sign-in still fails, the usual causes are a missed or expired two-factor verification code, an Apple server outage, a wrong device date and time that breaks certificate validation, or a VPN or proxy blocking Apple's authentication endpoints. Check Apple's System Status page, set Date & Time to automatic, disable any VPN, and re-enter a fresh 2FA code.

Why can I sign into TestFlight but see no builds to test?

TestFlight only shows builds for the exact Apple Account that received the invite. If you accepted the invitation or redeem code on one account but signed into TestFlight with a different one, no builds appear. A build older than 90 days has expired and disappears, and a developer can remove a build or hit the tester limit, which also leaves the list empty.

How long before a TestFlight build expires?

A TestFlight build expires 90 days after it is uploaded to App Store Connect. Once expired, testers cannot open or reinstall it and it cannot be reactivated. The developer must upload a new build, which restarts the 90-day window.

My Apple Account is locked or disabled, what should I do?

An Apple Account is usually locked or disabled after repeated wrong password attempts or for security reasons. Go to iforgot.apple.com to verify your identity and unlock it, then reset the password if prompted. If the email was never verified, confirm it from the verification message Apple sent before trying to sign in again.

Can a managed device or Screen Time block App Store and TestFlight sign-in?

Yes. Screen Time, under Content & Privacy Restrictions, can block account changes and App Store access, and a supervised or MDM-managed device can prevent installs, TestFlight, or account sign-in entirely. Disable the relevant Screen Time restriction, or ask your administrator to lift the device-management policy.