Questions

Hi Median team,

We're hitting a related but distinct Sign in with Apple issue on our app (Perscivo, com.perscivo.app) that also caused an App Store rejection today, on the same device type (iPad Air M3, iPadOS 27.0). Apple's reviewer reported "unable to use Sign in with Apple" as a hard failure, not the "Sign Up Not Completed" error above.

Following this thread's answer, we want to confirm: our integration goes through lovable.auth.signInWithOAuth("apple", ...) calling Supabase directly, similar to the original poster's setup. Our Social Login plugin IS enabled with Apple Sign In set to "Enable" (confirmed in-dashboard), and has been for several builds.

Given your answer above that signInWithOAuth alone can't trigger the native flow without correctly using Median's JavaScript Bridge, can you confirm:

Whether our specific implementation is correctly wired to trigger Median's native bridge, not just calling Supabase's OAuth method directly
Whether there's a known iPadOS 27-specific issue in the native shell's presentationAnchor(for:) implementation, specifically around using UIApplication.shared.keyWindow (deprecated) vs. the active UIWindowScene — this is required under iPadOS 27's mandatory scene-based lifecycle and could cause the native sheet to silently fail to present
Any other known iPadOS 27 compatibility gaps in the native Sign in with Apple flow

This is currently blocking App Store approval after 4 consecutive rejection rounds citing this exact issue. Appreciate any guidance.