Post

Replies

Boosts

Views

Activity

Waiting on App Review reply about demo sign-in access (Case 102983881736)
Hi App Review team, Our new iOS app was rejected on September 30, 2026 under Guideline 2.1(a) related to demo account access. We replied in App Store Connect with clarifying questions that same day and have not received a response in nearly a week. We also opened Case ID 102983881736 on Friday with no reply yet. The reviewer ran into two separate sign-in issues: Sign in with Apple: Our app is a companion app for an existing web platform, so it currently only allows sign in for accounts already set up on our website. The reviewer's Apple ID showed the expected "Please sign in on the web app to continue" message. Since Sign in with Apple uses the reviewer's own Apple ID, we can't provide standalone credentials for it. Google: Our Google demo account was hit with a Google "Verify it's you" security challenge. That prompt comes from Google, not our app. We can't reliably provide Google or Microsoft demo credentials, because we can't control when those providers trigger security checks during review. To solve both issues, we've built invite code support into the sign-in flow. When a user successfully signs in with Google, Microsoft, or Apple and no account exists for that email in our system, the app now prompts for an invite code instead of showing the "Please sign in on the web app to continue" message. For review, the reviewer would sign in with their own account and enter an invite code from our App Review Information notes, which links their OAuth sign-in to a fully seeded demo account. Before resubmitting, we need answers to two questions: Is this invite code approach acceptable for review? Does the reviewer need to test all three sign-in methods (Google, Microsoft, and Apple), or is one enough? This tells us whether to provide one invite code or a separate code for each method. We'd like to confirm this before resubmitting so the next review goes smoothly, but our launch is on hold until we hear back, so a reply soon would be greatly appreciated. All other fixes are complete. Once we have an answer, we will add the invite code(s) to our App Review Information notes and resubmit with a new build right away. Thank you.
0
0
27
2h
Waiting on App Review reply about demo sign-in access (Case 102983881736)
Hi App Review team, Our new iOS app was rejected on September 30, 2026 under Guideline 2.1(a) related to demo account access. We replied in App Store Connect with clarifying questions that same day and have not received a response in nearly a week. We also opened Case ID 102983881736 on Friday with no reply yet. The reviewer ran into two separate sign-in issues: Sign in with Apple: Our app is a companion app for an existing web platform, so it currently only allows sign in for accounts already set up on our website. The reviewer's Apple ID showed the expected "Please sign in on the web app to continue" message. Since Sign in with Apple uses the reviewer's own Apple ID, we can't provide standalone credentials for it. Google: Our Google demo account was hit with a Google "Verify it's you" security challenge. That prompt comes from Google, not our app. We can't reliably provide Google or Microsoft demo credentials, because we can't control when those providers trigger security checks during review. To solve both issues, we've built invite code support into the sign-in flow. When a user successfully signs in with Google, Microsoft, or Apple and no account exists for that email in our system, the app now prompts for an invite code instead of showing the "Please sign in on the web app to continue" message. For review, the reviewer would sign in with their own account and enter an invite code from our App Review Information notes, which links their OAuth sign-in to a fully seeded demo account. Before resubmitting, we need answers to two questions: Is this invite code approach acceptable for review? Does the reviewer need to test all three sign-in methods (Google, Microsoft, and Apple), or is one enough? This tells us whether to provide one invite code or a separate code for each method. We'd like to confirm this before resubmitting so the next review goes smoothly, but our launch is on hold until we hear back, so a reply soon would be greatly appreciated. All other fixes are complete. Once we have an answer, we will add the invite code(s) to our App Review Information notes and resubmit with a new build right away. Thank you.
Replies
0
Boosts
0
Views
27
Activity
2h