AppReviewX Log in

Testers cannot log in: test account problems

Shared test accounts, rate limits, email verification and two-factor: how to avoid blocking testers.

updated ·3 min read

In this guide

A tester who cannot log in cannot test anything. They will often give up quietly, and you get no feedback at all. Most login blocks are caused by how you set up the test account, not by the app. The fix is to look at login the way the tester sees it.

Why testers get locked out

  • One shared account for everyone. Several people log in at once. Your backend may allow only one active session, or treat many logins as suspicious and lock the account.
  • Rate limits and lockouts. Wrong-password limits, or limits per IP address, trigger when many testers share a network or retry quickly.
  • Email verification. The tester must confirm an address, but the email lands in spam, arrives late, or goes to an inbox they cannot open.
  • Two-factor authentication. The code is sent to a phone or email that only you control.
  • Expired or reset credentials. Test passwords that expire, or a data reset that wipes the account.
  • Environment mismatch. The build points at a staging server, but the account only exists in production, or the reverse.
  • Regional and device limits. Sign-in blocked by country, or by a device check the tester's phone fails.
  • Copy-paste errors. Passwords with look-alike characters or trailing spaces, sent in a chat message.

Set up login so testers do not get stuck

  1. Give each tester their own account where you can. If you must share one, make sure concurrent sessions are allowed.
  2. Relax limits for test accounts. Raise lockout and rate limits in the test environment, or exempt the test accounts.
  3. Skip or simplify verification for test accounts. Pre-verify the address, or use a fixed code in the test environment only. Never add a bypass to your production build.
  4. Offer a second way in. If you have social sign-in or a guest mode, say so. A tester with no working login can still look around.
  5. Write the instructions in the brief. Username, where to get the password, which build, which server, and what to do if login fails.
  6. Test the login yourself, on a clean phone, with a new account, before you invite anyone.

A checklist before you invite testers

  • Each test account logs in on a freshly installed build.
  • Two devices can use the same account at the same time, if shared.
  • The verification email arrives and is readable within a minute or two.
  • A two-factor step either works for testers or is switched off for test accounts.
  • Credentials have no look-alike characters, and are sent as plain text.
  • You know where to look when a tester reports "login failed".
  • There is a clear contact for login problems.

When a tester says "login does not work"

Ask for:

  1. The exact message on screen, or a screenshot.
  2. The username they used, never the password.
  3. The time of the attempt.
  4. Their phone model and app version.
  5. Whether it fails on Wi-Fi and mobile data.

With the time and username you can check your server logs and tell a typo from a lockout. For more on collecting usable evidence, see Tester screenshots unusable: how to ask for good ones.

On AppReviewX, testers give you private, structured feedback. If a login problem stops one, you can see it in their report instead of hearing silence. Start free.