mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 21:29:08 +03:00
Cemal Kılıç
92692240bf
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Bug fix ## What is the current behavior? When enabling Apple Sign-in in Studio, the form requires a valid JWT secret key whenever a client ID is provided. This blocks users who only use Apple native sign-in (iOS, macOS, watchOS, tvOS), where only the client ID (bundle ID) is needed and no secret is required. Resolves AUTH-1138 ## What is the new behavior? The secret key field is now optional, matching Google's provider behavior. JWT format validation still applies when a secret is provided, but leaving it empty is allowed. This supports native-only Apple sign-in configurations. ## Additional context The validation was simplified from two `.when` clauses (dependent on both `ENABLED` and `CLIENT_ID`) to a single `.when` (dependent only on `ENABLED`), matching the pattern used by the Google provider.