The next client (preview)

@ovok/native/next is the React Native edition of @ovok/core/next. It exports the same client API, keeps sessions in the device's secure store and supplies the crypto.getRandomValues that Hermes lacks. The native auth, CMS, questionnaire, image, socket, and health-sync modules use this client through OvokProvider from @ovok/core/next/react.

The Flutter SDK follows this contract, so its names match.

Create a clientCopy Anchor Link

import * as Crypto from 'expo-crypto';
import * as SecureStore from 'expo-secure-store';
import { Ovok } from '@ovok/native/next';

export const ovok = new Ovok({
  baseUrl: 'https://api.sandbox.ovok.com',
  tenantCode: 'your-tenant',
  secureStore: SecureStore,
  getRandomValues: Crypto.getRandomValues,
});

Mount one provider above the native modules:

import { OvokProvider } from '@ovok/core/next/react';

<OvokProvider client={ovok}>
  <App />
</OvokProvider>;

Health import reads the signed-in Patient from this session. It stores each provider cursor under the current tenant, project, and patient. A background Health Connect task must restore the same native client session and pass the matching patientId to runAndroidHealthConnectSync; the task refuses to import for another patient.

There is no clientSecret: anything shipped inside an app can be extracted from it.

Secure storageCopy Anchor Link

• Chunking: SecureStore warns past 2048 bytes per value, so each value is split across numbered entries.
• Keys: characters SecureStore rejects in a key, such as :, are written as _.
• Locked keychain: a read rejected before first unlock counts as "no session". The client never deletes anything because a read failed.

BluetoothCopy Anchor Link

Scanning, pairing, connecting and saving readings through this client are in Bluetooth on the next client.

Health dataCopy Anchor Link

Import HealthKit and Health Connect data through the @ovok/native/next/data-sync API. For Android headless imports and background-safe storage, see background sync on the next client.

The next client also persists measurement writes that cannot finish immediately. Retry them after connectivity returns with await ovok.measurements.offlineQueue.flush().

Everything elseCopy Anchor Link

Sign-in, FHIR, paging and errors work as in the JavaScript SDK's next client.

UI and content modulesCopy Anchor Link

These Next subpaths re-export the existing module APIs. Their previous import paths remain available.

API referenceCopy Anchor Link

Every export of @ovok/native/next, with signatures, props and types, is in the next API reference.