On this page
Build and device evidence
Know what is tested and what is device-dependent
Compilation coverage proves integration compatibility. Physical-device reports establish runtime behavior across real hardware and OS versions.
Supported floor
| React Native | 0.76 or newer with the New Architecture enabled |
|---|---|
| Android | API 24 or newer |
| iOS | The minimum iOS version supported by the host React Native release |
| Expo | Native prebuild or custom development build; Expo Go is not supported |
| Linking | React Native autolinking for Gradle and CocoaPods |
Automated coverage
The repository verifies TypeScript, Jest behavior, TurboModule contract parity, Android builds, iOS builds, package contents, example-app checks, and GitHub Pages synchronization. The exact active matrix is authoritative in GitHub Actions.
Physical-device evidence
Emulators and simulators cannot validate hardware, power, telephony, location, root, jailbreak, capture, accessibility, or timing behavior completely. A field can compile successfully and still be unavailable on a vendor build, OS release, permission state, or device class.
Availability rules
- Optional fields are omitted when their API, hardware, permission, cached value, or underlying read is unavailable.
- Android-only and iOS-only fields remain absent on the other platform.
- A missing field is not equivalent to an observed
false. - Default-off probes require explicit configuration and representative device QA.
- Transaction capture fields also depend on host-declared Android permissions and supported OS versions.
Use the typed signal catalog to inspect each probe's platforms, permissions, defaults, and field types.
Contribute a report
Run the example on a physical device, remove account identifiers, coordinates, local addresses, and other sensitive values, then submit the structured compatibility form.