Changelog

All notable changes to the VECU React Native Verifier SDK.

v1.2.0

Features

• New releaseVehicle(vin, verifiedClaims) method on VerifierSDK — posts to the Release BFF to release a vehicle after a successful verification. The SDK extracts the authorizationId from the supplied VerifiedClaims and handles bearer auth, transport, and error wrapping internally so host apps no longer need their own release helper.
• Returns ApiResult<undefined> — { ok: true } on success, or { ok: false, error } with a typed VerifierError on 4xx/5xx/network failure. Unlike checkAuthorization (which fails open), release errors propagate to the caller so apps can surface retry UX.

Migration Notes (for consumers upgrading from 1.1.x)

• Replace any custom release POST helper with sdk.releaseVehicle(vin, verifiedClaims). The SDK extracts authorizationId from the claims object itself — no need to pass it separately.

v1.0.2

Features

• NFC communication now uses the proprietary VECU AID (F056454355000001), preventing standard NFC readers from intercepting the handshake between wallet and verifier devices.
• Verification responses now include the custody authorization ID, giving host apps a direct reference to the underlying authorization record.

Fixes

• NFC sessions are now properly cleaned up when activation fails, preventing stale state on retry.
• NFC send no longer carries stale data forward after a failed attempt.

v1.0.1

Features

• Receive-from-wallet flow — a new ReceiveFromWalletView component that manages the full NFC tap, BLE connection, VIN transfer, and verification polling in a single component. Host apps provide only navigation callbacks.
• QR code fallback for BLE engagement when NFC is unavailable.
• BLE write-back of the presentation request URL to the wallet device.

Fixes

• Improved BLE scan matching and connection reliability.
• BLE read retry with automatic GATT cache refresh when the first attempt fails.

v1.0.0

Stable release

Highlights

• Stable React Native Verifier SDK release for client integrations.
• Full verification flow through VerificationView — displays a QR code, polls for status, and surfaces approved, denied, and expired results.
• Optional NFC delivery of the verification request via Android Host Card Emulation (HCE), so nearby wallet apps can receive the request by tapping instead of scanning the QR code.
• GPS proximity verification — the SDK automatically retrieves device coordinates and displays a proximity pass or warning badge on the approved screen.
• User-friendly error messages with status-specific guidance.

Client-Facing Guidance

• Host applications are expected to:
  • provide a VECU API bearer token
  • configure required native permissions for NFC, Bluetooth, and camera
  • mount VerificationView or use createVerifierSDK() for a custom UI
  • handle terminal callbacks (onApproved, onDenied, onExpired)

Notes

• Camera permission is not required — the SDK displays a QR code, it does not scan one.
• NFC delivery requires react-native-hce and Android HCE setup with the VECU AID F056454355000001.
• Receive-from-wallet flows require react-native-nfc-manager and react-native-ble-plx.

Requirements

• React Native >= 0.72.0
• React >= 18.0.0
• react-native-svg and react-native-qrcode-svg (peer dependencies)