[ Package conformance ]
Auth & Payments · >=2.0.0
@invertase/react-native-apple-authentication
performRequest returns deterministic simulated credentials — a fake JWT-shaped `identityToken` and `authorizationCode` that look real but fail any downstream Apple-public-key verification. consumer code that ships its own token verifier (which is the recommended SIWA pattern) hits a confusing "invalid signature" error rather than the unavailable-on-web branch. expo-apple-authentication dropped to 0.2 (PR #38) for the same pattern — this one is slightly higher only because the AppleButton component + enums + Android WebView signIn shape are still present.40%
API coverage
No visual conformance cases have been published for this package yet. The registry summary below describes what the compat layer implements.
Working (7)
AppleButton component with upstream string Style/Type constantsappleAuth support flagsError/Operation/Scope/State/UserStatus aliasesperformRequest validationgetCredentialStateForUsercredential revoke listenersappleAuthAndroid configure/signIn/Scope/ResponseType/Error
Missing (1)
real Sign-in-with-Apple OAuth flow via AppleID JS SDK (Service ID + HTTPS); real Apple-signed identityToken (current token is a fabricated JWT that fails consumer-side signature verification against Apple's public keys); real authorizationCode that a backend can exchange; AppleIDProvider availability detection; keychain-backed credential state across reloads; Android WebView OAuth redirect interception; native cancellation/error code propagation