HealthImportCard

HealthImportCard renders health-access state and per-type status for an app-provided HealthImportAdapter. It can also display optional SyncProgress values. Import the component from @ovok/native/ui and the adapter type from @ovok/native/bt-management.

import { HealthImportCard } from "@ovok/native/ui";
import type { HealthImportAdapter } from "@ovok/native/bt-management";

type HealthType = "steps" | "weight";

const adapter: HealthImportAdapter<HealthType> = {
  getStatus: async (type) => readPermissionStatus(type),
  request: async (types, background) => {
    await requestAppHealthAccess(types, { background });
  },
};

<HealthImportCard
  types={["steps", "weight"]}
  adapter={adapter}
  background
  labelForType={(type) => healthTypeLabels[type]}
/>

This is an adapter-driven UI component. It does not configure HealthKit or Health Connect, and it does not start the SDK's DataSync import pipeline. For those integrations, see DataSync and the HealthKit and Health Connect guide.

PropsCopy Anchor Link

Every prop, with its type and description, is listed in the @ovok/native/ui API reference.

Status and request behaviorCopy Anchor Link

The component calls getStatus for each listed type on mount and after a successful request. It shows these built-in labels:

The card is enabled only when every listed type is authorized. It marks refused types with an additional notice. If getStatus fails, the card displays the error and keeps that type's previous status, if one was already available.

Turning the card on calls adapter.request(types, background) and refreshes the statuses when the promise resolves. Turning it off only changes local UI state. The adapter contract has no revoke, stop, or cancel method, so switching off does not revoke OS permission or stop an app-owned import service. The card does not subscribe to permission changes made elsewhere; refresh or remount it from app-owned state when access may have changed in system settings.

The built-in copy goes through react-i18next with the English text above as the default, so it renders unchanged until your app adds these keys to its locale resources:

An explicit title prop still wins over the translated title. statusLabels and reasonLabels customize only the nested sync-progress list; type names come from labelForType.

See Reusable flows for the app integration boundary.