react-native-health-connect

Install

npm install react-native-health-connect

npm install expo-build-properties --save-dev

Registry and repository facts

Read from npm and the repository by a script, not typed by hand. Where the metadata does not state something, the row says so. Dates are shown as dates, with the gap to our read, rather than as a verdict on whether the project is alive.

Registry

npm: react-native-health-connect

Latest version

4.1.3, published 2026-08-0658 days before our 2026-10-03 read

First published

2022-05-11 · 46 versions published

Licence

MITpackage.json license

Platforms

Androidregistry description: "React native library for health connect (Android only)"

Requires

@expo/config-plugins >= 6.0.2 · expo * · react * · react-native *package.json peerDependencies

Repository

matinzd/react-native-health-connect

Last commit, default branch

2026-08-2638 days before our 2026-10-03 read · read by git on 2026-10-03

GitHub signals

416 stars · 58 open issues and PRs · not archived · last push to any branch 2026-08-26GitHub API, read 2026-10-03

Registry description: “React native library for health connect (Android only)”

What the README warns about

Each item is the project’s own statement, checked on 2026-10-03, quoted where the wording matters.

• Bare apps register a permission delegate. For the React Native CLI template, from version 2 on, the README adds HealthConnectPermissionDelegate.setPermissionDelegate(this) to MainActivity.onCreate. Expo projects skip this: the README says the bundled Expo module registers it.

  “In order to handle permission contract results, we need to set the permission delegate.”

  Source: README

• expo-health-connect is now a build error. The README says that leaving the old package installed alongside v4 fails the Android build with a duplicate expo.modules.healthconnect.HealthConnectPackage class.

  Source: README

• Device requirements. The README says Health Connect must be installed on the user's device, is part of the Android framework from Android 14, and needs minSdkVersion=26.

  Source: README

• React Native version. The README asks for React Native 0.71 or higher, with the latest patch, for v2 and later, and lists support for both the old and new architectures.

  Source: README

The API underneath

A wrapper inherits every rule of the API it calls. These pages cover that layer directly.

• Health Connect integration guide →The Android API these packages wrap: permissions, records, the 30-day window.
• Health Connect record reference →Every record class with Google's fields, permission strings and aggregate metrics — check the type you need exists before blaming the wrapper.
• HealthKit types vs Health Connect records →Which record a HealthKit type maps to, and the pairs that look equivalent but are not.
• Health Connect returns no data →The usual causes when a read comes back empty, whichever wrapper you use.
• Migrate from Google Fit to Health Connect →If this package is replacing react-native-google-fit in your app.
• Health SDK release tracker →This package's GitHub releases, refreshed daily.

Other React Native packages on this list

React Native health data libraries: every package side by side, and how to choose →

• react-native-health1.19.0 · 2024-10-15Apple HealthKit, on iOS only.
• @kingstinct/react-native-healthkit16.0.0 · 2026-09-18Apple HealthKit, on iOS.
• expo-health-connect0.1.1 · 2024-07-31 · deprecatedNothing on its own: it was an Expo config plugin that configured react-native-health-connect at prebuild time.
• react-native-google-fit0.22.1 · 2025-10-08The Google Fit API on Android, through Google Play Services and an OAuth 2.0 client configured in Google Cloud Console, according to the README's requirements.

Questions

Does react-native-health-connect work on iOS?

No. The registry description marks it Android only, because Health Connect is an Android platform. Its README names @kingstinct/react-native-healthkit and react-native-health as the iOS alternatives, so a cross-platform React Native app installs one of those next to it.

Do I still need expo-health-connect with react-native-health-connect?

No. Since v4 the Expo config plugin and the Expo module that registers the permission delegate ship inside react-native-health-connect. The README says to uninstall expo-health-connect, replace it with react-native-health-connect in the app.json plugins array and re-run prebuild with --clean; leaving both installed fails the Android build with a duplicate class.

What does HealthConnectPermissionDelegate do in react-native-health-connect?

It lets the library receive the result of the Health Connect permission request. The README's MainActivity example sets it in onCreate with the comment that it is needed to handle permission contract results. React Native CLI apps add it themselves from version 2 on; Expo apps do not, because the bundled Expo module registers it.