Skip to content

Change appAttestation from object to boolean flag#84

Closed
stevenclouston wants to merge 4 commits intomainfrom
stevenclouston/app-attestation-boolean-flag
Closed

Change appAttestation from object to boolean flag#84
stevenclouston wants to merge 4 commits intomainfrom
stevenclouston/app-attestation-boolean-flag

Conversation

@stevenclouston
Copy link
Copy Markdown
Contributor

Summary

  • Changes appAttestation parameter from AppAttestation object ({ token, keyId }) to a boolean flag
  • Native SDKs now generate attestation internally (iOS: App Attest, Android: Play Integrity), so callers only need to signal whether attestation should be enabled
  • Updates all layers: TypeScript types, TurboModule spec, iOS bridge (Obj-C + Swift), Android bridge (Kotlin)
  • Removes the AppAttestation TypeScript interface (no longer needed on the JS side)

Depends on

Test plan

  • iOS: verify addCredential({ appAttestation: true }) triggers App Attest and enrolls successfully
  • iOS: verify addCredential({}) (no attestation) still works
  • Android: verify build compiles with boolean parameter change

Remove AppAttestationProvider enum from public API. Provider is now
hardcoded internally by each native SDK (APP_ATTEST for iOS, PLAY_INTEGRITY
for Android). AppAttestation interface now just takes token and optional
keyId. Also bumps native SDK deps and version to 2.8.0-alpha.2.
The native SDKs now generate attestation internally, so callers
only need to signal whether attestation should be enabled rather
than passing the attestation token and keyId.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant