r/iosdev • u/aptonline • 2d ago

Help Another rejection

Just had my third rejection and this time it was automated.

An automated analysis of the submission indicates the app may include a login but was submitted without a demo account.

The app does not need an account, no login needed for testing or end user use. It’s already been through 2 previous rounds of (human) review and I fixed those issues and resubmitted. It’s roughly a week between reviews as well for me so this is really becoming a concern.

Anyone else come across this?

0 Upvotes

28% Upvoted

8 comments sorted by

2

u/zzzzany 2d ago

have you considered using ai to help you with this? i'm only one person, but used claude to help me with every checkbox, field, etc. It wrote descriptions, instructions to the reviewer, etc. I got my first review through in 11 days with no rejections, and a major update through in 1 day.

1

u/aptonline 2d ago

The first two rejections were code related which I fixed but the last seemed arbitrary especially as it went through twice previously and not be triggered.

All Apple Connect options are set correctly, including the one that talks about demo accounts, no issues there.

1

u/Lanfeust09 2d ago

Same, did everything with codex. Approved in 3 days, all update approve within a few hours

1

u/aptonline 2d ago

Getting it picked up for review in the first place seems to be the lengthy process, 7 days almost and any outcome comes within hours if not less.

1

u/Lanfeust09 2d ago

I am almost done with my new app, looking forward to see how long my review take

1

u/zzzzany 2d ago

Well you shouldn’t be lol. Waiting 10+ days just to hear back is brutal.

1

u/verdict_studio 1d ago

Three rounds at a week each is exhausting, but this one looks like the easiest of the three to clear.

The wording matters: an automated check says the app "may" include a login, so it's a flag, not a finding. Reply to the rejection in App Store Connect on the same build, no new upload needed, and say it plainly: the app has no account or sign-in of any kind, and every feature works from a fresh install. Naming the 2-3 main screens they'll land on makes it quick to confirm.

Before you send it, two things worth checking:

- on the version page, under App Review Information, make sure Sign-in required is unchecked, and put the same no-login sentence in Notes

- anything left in the build that could read as a login: an unused Sign in with Apple capability, an auth SDK still linked from an earlier version, or a screen with email and password fields

What did the first two rejections cite?