fix: gate KYC on device support and patch Segment deeplink crash

[transphorm]

Addreseses

• https://self-rfe.sentry.io/issues/7592860126/?project=4508860282503168&query=is%3Aunresolved&referrer=issue-stream
• https://self-rfe.sentry.io/issues/7414646186/?project=4508860282503168&query=is%3Aunresolved&referrer=issue-stream
• https://self-rfe.sentry.io/issues/7593735569/?project=4508860282503168&query=is%3Aunresolved&referrer=issue-stream

Summary

• Adds a two-layer device-support gate for KYC (Didit) on Android: Didit's MediaPipe auto-capture links aligned_alloc, which Android only provides from API 28, so launching it on Android 8 and below throws an uncatchable UnsatisfiedLinkError in a background coroutine and crashes the app.
• Layer 1 (service, fail-closed): launchKycVerification returns a failed result with a new unsupportedDevice error type instead of calling the SDK; the KYC failure screen disables retry for it via isRetryableKycFailure.
• Layer 2 (UI, never offer): every KYC entry point — ID picker's "View other supported IDs", NFC/MRZ/camera trouble screens, registration fallback screens, Aadhaar upload error, data confirmation, and the camera-permission alert — hides its KYC offer via useKycLauncher().isKycSupported; fallback handlers no longer flip the onboarding funnel branch to kyc before the support check passes.
• Patches @segment/analytics-react-native@2.23.0 to fix a bridgeless-mode (New Architecture) crash in trackDeepLinks, mirroring upstream fix(android): crash on New Architecture in trackDeepLinks segmentio/analytics-react-native#1146.

Flow

flowchart LR
  subgraph Entry points
    A[IDPickerScreen] & B[Trouble / fallback screens] & C[Camera permission alert]
  end
  A -->|showKycOption| G{isKycSupportedOnDevice}
  B -->|"isKycSupported (hide button)"| G
  C -->|onFallback only if supported| G
  G -->|supported| H[useKycLauncher.launchKycVerification]
  G -->|unsupported| M[Device-not-supported modal / hidden]
  H --> S[kycService.launchKycVerification]
  S -->|unsupported guard| F["failed: unsupportedDevice (canRetry=false)"]
  S -->|supported| D[Didit SDK startVerification]

Loading

Changes

React Native app

• integrations/kyc: new KYC_MIN_ANDROID_API_LEVEL (28), KYC_UNSUPPORTED_DEVICE_MESSAGE, isKycSupportedOnDevice(), isRetryableKycFailure(); launchKycVerification fails closed with unsupportedDevice before touching the Didit SDK.
• useKycLauncher: exposes isKycSupported, shows a "Device not supported" modal if a launch is somehow triggered anyway, and routes the fallback modal through the same check.
• selfClientProvider: the kyc document-type branch navigates straight to KycFailure (no retry) on unsupported devices, and canRetry now respects isRetryableKycFailure.
• Screens (IDPicker, DocumentNFCScan, DocumentNFCTrouble, DocumentCameraTrouble, DataConfirmation, RegistrationFallbackNFC/MRZ, AadhaarUploadError, LogoConfirmation, DocumentOnboarding): KYC buttons/options render only when supported; setOnboardingBranch('kyc') only fires when the launch can proceed; the camera-permission alert omits "Try Alternative Verification" when unsupported.

SDK core

• id-selection-screen accepts an optional showKycOption prop (default true, backwards-compatible) to hide the limited-security IDs section.

Tests

• New coverage for the service guard, isRetryableKycFailure, and the hook's unsupported-device modal; screen/provider test mocks updated for the new isKycSupported / isKycSupportedOnDevice surface.

Config/infra

• pnpm patch for @segment/analytics-react-native@2.23.0 replacing the ReactNativeHost.reactInstanceManager lookup (unsupported on New Architecture) with reactApplicationContext.getNativeModule; drop once a release newer than 2.23.0 ships the upstream fix.

Test Plan

• pnpm --filter @selfxyz/mobile-app exec jest on affected suites (kycService, useKycLauncher, selfClientProvider, DataConfirmation, DocumentNFCTrouble, navigation, cameraPermission) — 61 tests passing
• tsc --noEmit and eslint clean on changed files
• Manual: Android < 9 device/emulator sees no KYC offers anywhere and gets a non-retryable failure screen if the KYC doc type is forced
• Manual: deeplink open on New Architecture Android build no longer crashes in Segment trackDeepLinks

Native Consolidation Checklist

• CONTRACTS.md reviewed - no unintended contract changes
• Layer 1 bridge contract tests pass
• Layer 3 builds pass (app iOS, RN test app iOS, RN test app Android)
• No new native business logic added (Segment patch mirrors an upstream fix; logic stays in TypeScript)

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • KYC/alternative verification options are now shown only when KYC is supported on the current device.
  • Added a clearer “Device not supported” message and flow when KYC can’t run.
• Bug Fixes
  • Retry buttons now appear only for failures that are retryable; unsupported-device failures no longer suggest retry.
  • Improved reliability of deep-link handling for analytics tracking.
• Documentation / Tests
  • Updated tests to cover unsupported-device and retryability behavior.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
self-webview-app	Ready	Preview, Comment	Jul 12, 2026 3:13pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds Android device-support and KYC retryability checks, propagates support state through KYC launchers and document screens, conditionally hides unsupported alternative-verification paths, and patches Segment native deeplink dispatch.

Changes

KYC device support gating

Layer / File(s)	Summary
KYC support and retry contracts app/src/integrations/kyc/*, app/tests/src/integrations/kyc/kycService.test.ts	Adds Android API-level support constants, support and retryability helpers, guarded verification, re-exports, and platform-specific tests.
Launcher hook and modal handling app/src/hooks/useKycLauncher.ts, app/tests/src/hooks/useKycLauncher.test.ts	Adds unsupported-device modal handling, support guards, retryability-based failure navigation, isKycSupported, and coverage for unsupported-device flows.
Provider failure routing app/src/providers/selfClientProvider.tsx, app/tests/src/providers/selfClientProvider.test.tsx	Routes unsupported devices to KycFailure without retry and derives retryability from verification results.
Alternative-verification screen gating app/src/screens/documents/aadhaar/*, app/src/screens/documents/scanning/*, app/src/screens/documents/selection/*, matching tests	Uses device support to conditionally render or execute alternative-verification actions and updates related test mocks.
ID selection visibility app/src/screens/documents/selection/IDPickerScreen.tsx, packages/mobile-sdk-alpha/src/flows/onboarding/id-selection-screen.tsx	Adds showKycOption and gates the KYC footer entry based on device support.

Estimated code review effort: 3 (Moderate) | ~30 minutes

Segment analytics deeplink patch

Layer / File(s)	Summary
SovranModule retrieval and patch registration pnpm-patches/@segment__analytics-react-native@2.23.0.patch, pnpm-workspace.yaml	Retrieves SovranModule directly from reactApplicationContext and registers the patch for the Segment package.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes both primary changes: gating KYC based on device support and patching the Segment deeplink crash.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/minor-rn-bug-fixes

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}