App rejected because malfunctional Apple SignIn but cannot be reprodeced

Question

someonedisruptapplepls OP

Created 3d

Replies 1

Boosts 0

Participants 2

Hi everyone,

Our recent app update was rejected under Guideline 2.1 – App Completeness, with the note:

“The app was unresponsive when we tapped on Sign in with Apple.”

Device: iPad Air (5th generation) OS: iPadOS 26.1

However, we’ve tested this thoroughly and can’t reproduce the problem at all.

Here’s what we’ve done so far:

Tested both on simulator and real devices (iPhone and iPad).

Tried combinations of:

Logged in / not logged in to iCloud

Apple ID linked / not linked to our app

In all cases, Sign in with Apple works as intended — no freezing or unresponsiveness.

We also recorded videos showing successful sign-in on simulator (iPad Air, iOS 26) and iPhone 13 mini simulator:

We replied to App Review asking whether they were using a simulator (since “Sign in with Apple” often fails there unless the test Apple ID is properly set up). We also provided steps and links explaining that you need to: Create a test account with a real email. Sign in at iCloud.com, and complete security setup / agree to terms, in order for that test account to be recognized in a simulator environment.

From our end, everything functions correctly — so it’s quite frustrating to hear it was “unresponsive.”

Has anyone encountered similar false positives with Sign in with Apple on simulator tests? Is there a recommended way to clarify or escalate with App Review when we’re confident it’s an environment issue on their side?

Any advice from others who’ve handled similar rejections would be greatly appreciated 🙏

Boost

Answer 1

Tomato OP

2d

They are known to use an iPad to test the iOS app you submit regardless of the intended platform. I would ask them to send me a screen-capture video. But I don't know if they comply. I don't remember if they have ever sent me a screen-capture video. It's true that they sometimes go terribly wrong. Back in July, they claimed that nothing had happened in making an in-app purchase. It has turned out he or she failed to scroll down further and tapped an image, not a button. The same reviewer also claimed that a user would not be able to request customer support at our web site when in fact it was just the matter of scrolling down further, again, to find a comment box.

I would send them a screenshot after circling the button they are supposed to tap to make sure he or she is not off the track.

It's true that I sometimes make a mistake and deserve to get my software submissions rejected. But reviewers collectively make more mistakes than I do. I say they are wrong 2/3 of the times.

0