TestFlight Beta App Review: Guideline 2.1(a) rejection without specific feedback

Question

KennyBergstrom OP

Created 1w

Replies 1

Boosts 0

Participants 2

Hello,

I’m looking for some advice regarding a TestFlight Beta App Review issue.

My app, MyStory, was rejected twice under Guideline 2.1(a) with the same general message: App Review was unable to successfully access all or part of the app.

In the first review, Apple specifically asked us to provide a demo account with content demonstrating the app’s functionality. We followed those instructions for Build 3:

• Created a dedicated demo account with sample content in all four sections. • Added the username and password under Beta App Review Information. • Added testing instructions. • Replied to App Review with the credentials and instructions.

Build 3 was nevertheless rejected again under the same Guideline 2.1(a), without specifying which part of the app was inaccessible.

We have tested the app and the demo account ourselves, and everything works as expected on our devices. The app can also be used without an account, and users can create an account directly within the app.

We have now replied to App Review asking them to identify the specific screen, step, or functionality they were unable to access. We are currently waiting for a response.

Has anyone experienced a similar situation? In particular, I would appreciate advice on how to get a more specific explanation from App Review, or whether there is an appropriate way to escalate the issue if they cannot identify what was inaccessible.

I’m also wondering how reliable the 24-hour response timeframe is in practice. It has now been more than a day and a half since I replied to App Review. Should I expect a response within a few days, or can Resolution Center replies sometimes take considerably longer?

Thank you.

Answer 1

GetResubmit OP

1w

Since the reviewer still could not access the app after you added the demo account, I would treat this as an environment or account-state problem rather than upload another build immediately.

Test the exact Beta App Review credentials from a clean installation and a network outside your development environment. Verify that:

the account is already activated and does not require email verification, MFA, an invitation, or acceptance of updated terms;
it is not restricted by region, IP address, device count, rate limits, or an expired session;
all four sections contain persistent sample data and use the same permissions as intended;
the production backend used by the submitted build is available without VPN or internal configuration;
the guest path and the demo-account path are both described separately in Beta App Review Information.

Attach a short recording starting from a clean install, plus timestamped authentication and API logs for a successful login using that exact account. Then ask Apple to provide the failing screen, timestamp, or step so you can correlate it with the server logs.

Because this is TestFlight review, I would first update the Beta App Review instructions and evidence and wait for the requested clarification. A new binary is only useful if you identify an actual client-side defect.