Yes it is, I think the hasSeenConsent logic was exactly the mistake causing Apple's reviewers to not see the consent screen. I did some more research and found that the best approach is to remove the hasSeenConsent check entirely. Now the consent screen only checks hasConsented — if the user hasn't explicitly agreed, the consent screen blocks the entire app as the very first view, even before the loading screen. This guarantees the reviewer (and every user) sees it on every launch until they accept, or they can deny it, but won't be able to use any AI features. Resubmitting now — hopefully it finally passes! Appreciate the help.

Thank you for the feedback. Let me clarify: My app is a SwiftUI iOS fitness app called GymFusion. It uses Anthropic's Claude AI API to power features like meal photo scanning, body composition analysis, and workout coaching. The rejection is solely about Guidelines 5.1.1(i) and 5.1.2(i) — the app shares user data with a third-party AI service (Anthropic) and Apple says the app doesn't clearly disclose this or ask for permission. There are no in-app purchase issues — apologies for any confusion. Here's what I've implemented: The app's entry point (RootView) shows the AI consent screen as the first view on every launch. It's not a sheet or popup — it's embedded in the view hierarchy: if auth.isLoading { // Loading screen } else if !consentManager.hasConsented && !consentManager.hasSeenConsent { AIConsentView() // Consent blocks the entire app } else if auth.isAuthenticated { MainTabView() } else { AuthView() } The consent screen: Lists all data shared (photos, workout history, body measurements, fitness profile) Names Anthropic (Claude AI) as the recipient Requires 3 checkboxes before "I Agree" is enabled Resets on every app launch until accepted The problem: Apple's reviewer says "we were not presented with the consent prompt on launch or anywhere else in the app" — but it appears correctly on all my test devices (iPhone and iPad simulators, physical devices). Has anyone experienced App Review not seeing a view that renders correctly in their own testing? Could there be something about how SwiftUI conditional views render on the reviewer's device that differs from local testing?