Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Apple rejected my app because the reviewer cannot log in

Short answer

Apple's guideline 2.1 says to include demo account information if your app has a login, and to turn on your back-end service. The usual failures: the account expired, a one-time code goes to your phone, or the server was off or blocked. Provide a stable account and test it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The rejection says they could not sign in.
  • My app sends a code to my phone number or email.
  • The demo account worked when I made it a month ago.
  • The server is only reachable from my office or country.
  • The reviewer needs an account that already has data.

Why does this happen?

  1. No demo account was given

    Guideline 2.1 asks you to include demo account info if your app includes a login.

  2. The back end was off

    The same guideline says to turn on your back-end service. A sleeping test server or paused cloud project looks like a broken app.

  3. Two-step codes go to the wrong person

    A code sent to your own phone cannot be read by a reviewer in another country.

  4. The account changed or expired

    Passwords reset, trial periods end and test data gets cleaned up between your last check and the review.

What can I do about it today?

  1. Test the exact credentialsSign out and log in with what you wrote in the review notes, on a fresh install.
  2. Remove the personal code step for that accountAsk your developer for a demo account that does not need your phone.
  3. Keep the server onMake sure it is running and not limited by location or IP while the review runs.
  4. Fill the account with sample dataAn empty app can look unfinished.
  5. Reply in Resolution CenterGive the working details and say what changed. Apple's notes field is for the reviewer, not for passwords you reuse elsewhere.

When should I bring someone in?

  • The app signs in only with a phone number or a third-party service.
  • The server is behind a firewall you do not control.
  • Two rejections for the same reason.

How do I handle it?

  1. Create a dedicated review accountI add it with fixed credentials and realistic sample data.
  2. Bypass personal verification safelyThe account skips the one-time code, only for that account, and does not weaken real accounts.
  3. Run the real buildI test the build that is submitted, on a clean phone, with the server as the reviewer will see it.
  4. Write review notesThey say where to log in and what to try.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I use my real account?

No. Use one made for review, and remove or change it afterwards.

Does turning on the server really matter?

Apple names it in guideline 2.1.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.