💬
Get Help
D
Darkodante

Apple Sign In (Supabase + custom action) fails with AuthorizationError 1000 on TestFlight

Database & APIs

Hi,

Stuck on Sign in with Apple and hoping someone's beaten this. Auth is Supabase (not Firebase), so I'm using a custom action, not FF's native Apple action.

Code: SignInWithApple.getAppleIDCredential() + SupaFlow.client.auth.signInWithIdToken(provider: OAuthProvider.apple, ...) with a hashed nonce. Compiles clean. crypto added as a custom pub dependency; sign_in_with_apple is auto-provided by FF (7.0.1).

Symptom: On tap, the native Apple sheet never appears. Added error handling — it consistently returns:

SignInWithAppleAuthorizationException(AuthorizationErrorCode.unknown, ... com.apple.AuthenticationServices.AuthorizationError error 1000.)

Real device via TestFlight, not simulator.

Error 1000 points to the com.apple.developer.applesignin entitlement missing from the build. My question: does enabling "Supabase Apple Authentication" actually inject that entitlement when Apple sign-in is done via a custom action rather than FF's native action? If not, how do you get it into the managed build without exporting code / using Xcode (no Mac)?

Anyone with Supabase + custom Apple sign-in working on TestFlight — what got the entitlement in?

What have you tried so far?

  • App ID has Sign in with Apple capability enabled

  • Services ID + Supabase callback return URL configured; Supabase Apple provider enabled with Client IDs + secret

  • Apple's own auth page loads fine when I hit the Supabase authorize URL in a desktop browser, so the Apple/Supabase config is correct

  • Settings → Integrations → Supabase → "Enable Apple Authentication" is toggled ON

  • Rebuilt multiple times after enabling it

Did you check FlutterFlow's Documentation for this topic?
Yes
1
1 reply