Skip to content

Common rejection

Apple says my app crashed or they couldn't sign in

By Huruy Kidanemariam, who shipped Beles and EBT Finder to the App Store. Updated .

The short answer

The reviewer couldn't use your app. Usually that's a missing or broken demo account, a crash on their device, or a sign-in that works in a browser but fails inside the app.

How to fix it

  1. Add a demo account in App Store Connect under App Review Information, with two-factor turned off and sample data inside.
  2. If people sign in with a code sent by email or text, give the reviewer a way in that doesn't need their inbox: a demo account with a password works.
  3. Test on a real iPhone through TestFlight, not just the simulator or a browser.
  4. Check the crash report Apple attached, or the crash logs in App Store Connect.
  5. Point the app at your final web address. Inside an app, a redirect that browsers follow quietly can break sign-in.
  6. If you offer Google sign-in, set it up inside the iPhone app too. Google blocks its sign-in page inside wrapped web apps.
  7. Check your server too. If sign-up fails there, the reviewer sees your app failing. Fix it, then reply to Apple; you may not need a new build.
  8. Make sure nothing the reviewer needs is switched off, region-locked or invite-only.

What I ran into

The first Beles build called a web address that redirects. Browsers follow that without anyone noticing; the iPhone app didn't, so sign-in failed. The fix was one line: point the app at the final address. It shipped in build 2. EBT Finder's one rejection was the opposite: the app was fine, but a broken database rule made every new sign-up fail. I fixed it on the server, explained it to Apple, and it was approved without a new build.

Questions

It works on my phone. Why not theirs?
Reviewers use a fresh device, a fresh account and often a different network. Test it the way they will: new install, demo account, TestFlight.

Apple calls this Guideline 2.1, App Completeness in the App Review Guidelines.