Repository navigation
test: pin biometric credential storage format - #584
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (2)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
Included review availability: This review used your included allowance. 5 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 8 reviews per hour. 📝 WalkthroughWalkthroughThe change adds a serialized test suite for biometric credential storage contracts and a v1 JSON fixture. The tests cover Secure Enclave key attributes, policy values, JWK and signature encodings, Keychain metadata, v1 record decoding and encoding, unknown-field handling, identifier normalization, and reinstall-marker key formatting. Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This change only adds tests that pin the biometric credential storage format, so it does not affect runtime behavior. No actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 14 functions across 1 files. (1 skipped: 1 unsupported.)
Comment |
CI pausedCI does not run automatically on pull request updates. Before merging, manual CI must be run and pass for the latest commit. When this PR is ready for CI, a Clerk organization member can comment:
Clerk members with write access can also use the quick action below:
|
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
c3cdf7d to
cfbe1f0
Compare
What & why
@clerk/expo-biometricsreads and writes the same on-device biometric credential store as clerk-ios, so an app using both it and the prebuilt UI sees one set of credentials (the server allows one active credential per client, platform and app). That makes the current storage format a cross-SDK dependency. These tests pin it so a change here fails loudly instead of silently breaking the Expo module:dev.clerk.trusted_device.<localKeyId>, key attributes and per-policy access control flagstrustedDeviceCredentialsgeneric-password item and its attributesr||ssignature conversionNo behavior change.
What to focus on
<bundle id>.clerk.appservice (since refactor: share the device token through the Keychain access group #579). Expo doesn't use an access group, so these tests cover the default setup only.🤖 Generated with Claude Code