`DataSync`

Import DataSync from @ovok/native/data-sync. It is a compound API: its static members provide platform authorization, importing, and manual request UI. DataSync itself simply renders its children. It does not create a client, own authorization state, or start an import.

import { DataSync } from "@ovok/native/data-sync";

<DataSync.AndroidHealthConnectAuthorizationProvider
  readIdentifiers={["Weight"]}
>
  <DataSync.AndroidHealthSync dataToSync={androidDataToSync} />
</DataSync.AndroidHealthConnectAuthorizationProvider>;

Members

Member	Use
`AppleHealthAuthorizationProvider`	Request and observe HealthKit authorization.
`AppleHealthSync`	Read HealthKit samples and save mapped observations.
`AndroidHealthConnectAuthorizationProvider`	Initialize Health Connect and request read/write or background-access permissions.
`AndroidHealthSync`	Read Health Connect records and save mapped observations.
`ManuallyRequestSheet`	Build an app-owned permission prompt using a bottom-sheet modal and compound UI pieces.

Use the matching platform provider and sync component together. The providers handle permission state; the sync components use the initialized @ovok/core client and patient profile from context.

When to use the namespace

Use the static members when composing one platform flow. You do not need to render <DataSync> around them; render the provider directly around its sync component. Use SyncProgressList separately if the screen needs the SDK's progress UI.

For platform setup and a complete integration walkthrough, see the HealthKit and Health Connect guide.

Members​

When to use the namespace​

Members

When to use the namespace