URGENT: iOS App Store Rejection Expert (React / Capacitor / Apple SSO)

We are looking for an experienced iOS developer who is intimately familiar with Apple’s App Store Review Guidelines (specifically Guidelines 3.1.1 and 2.1(a)) and has experience with React and Capacitor to help us break out of a frustrating App Store rejection loop. About the Project: We have a B2B enterprise SaaS platform (built with React/Next.js on the web) for home inspection businesses. Our mobile app is a React web app wrapped in Capacitor for iOS. The app is purely an "Enterprise Companion App" — it has no in-app purchases, and accounts are only provisioned by Organization Admins via our web platform. The Problem (The App Store Catch-22): Our login screen currently offers Email/Password, Sign in with Google, and Sign in with Apple. Guideline 3.1.1 Rejection: Initially, Apple rejected us because unrecognized users could tap "Sign in with Apple/Google" and auto-provision a new account. They claimed this bypassed In-App Purchases since it was an account registration feature. Our Fix: We updated the Capacitor React code so that if an unrecognized Apple ID attempts to log in, it immediately logs them out and throws an "Account Not Found" error to prevent account creation. Guideline 2.1(a) Rejection: Now, Apple is rejecting us because the reviewer taps "Sign in with Apple," gets blocked (as intended by our fix), and flags the feature as a "Bug" (Sign in with Apple is not functional). Apple support is giving us automated, non-helpful responses. We previously had issues with their 'In-App Purchases' guidelines as we are an enterprise solution and were trying to bypass their 30% comissions. It seems we may be through that now. The Tech Stack: Frontend: React (Auth logic is in AuthView.jsx) Mobile Wrapper: Capacitor Backend/Auth: Firebase / Firestore Build Environment: We use MacInCloud to compile our Xcode builds. What We Need From You: We need an expert to review our current AuthView.jsx logic and implement a solution that completely satisfies Apple. We are open to your expert recommendation on the best path forward, which may include: Implementing a "Dead-End Empty State" (letting the SSO succeed technically so it's not "broken," but dumping the user onto a screen that says "Workspace Not Found" so no real account is created). Conditionally hiding the Apple/Google SSO buttons specifically on the iOS native build (leaving only Email/Password) to bypass the Guideline 4.8 / 3.1.1 requirements entirely. We would like you to guide us through to the finish line, to help us understand what is the best path forward to get through their long and difficult review process. Required Skills: Expertise in Apple App Store Review Guidelines and dispute resolution. Strong React and JavaScript skills. Experience with Capacitor and Xcode deployments. If you have successfully navigated this specific Apple SSO / B2B App Store paradox before, please start your proposal with "I know how to fix this loop" so we know you read the description.