react-native-health

Install

yarn add react-native-health

pod install

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

Latest version

1.19.0, published 2024-10-15718 days before our 2026-10-03 read

First published

2020-09-21 · 40 versions published

Licence

MITpackage.json license

Platforms

not stated in registry metadata

Requires

react-native >=0.67.3package.json peerDependencies

Repository

agencyenterprise/react-native-health

Last commit, default branch

2024-10-15718 days before our 2026-10-03 read · read by git on 2026-10-03

GitHub signals

1,163 stars · 157 open issues and PRs · not archived · last push to any branch 2026-04-27GitHub API, read 2026-10-03

Registry description: “A React Native package to interact with Apple HealthKit”

What the README warns about

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

• New features are on hold. A README section dated August 2023 says the maintainers are building a Swift version with a new interface, are holding off on new features until then, and welcome pull requests for critical bug fixes and dependency issues.

  “As we are fully focused in it, we're temporarily holding off on introducing new features.”

  Source: README

• No Expo Go. The README says the package cannot run in the Expo Go app and points to custom development clients instead.

  “This package is not available in the Expo Go app.”

  Source: README

• Background delivery is native setup. The README's background section adds #import "RCTAppleHealthKit.h" and [[RCTAppleHealthKit new] initializeBackgroundObservers:bridge]; to AppDelegate.m — an Objective-C app delegate, which newer Swift-template projects will need to bridge.

  Source: README

• Two repository names, one repository. The npm metadata still names agencyenterprise/react-native-healthkit, while the README and our SDK release tracker use agencyenterprise/react-native-health. On 2026-10-03 a git fetch of both addresses returned the same default-branch commit, so they are one repository under an old and a new name.

  Source: npm registry metadata and a git fetch of both URLs

The API underneath

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

• HealthKit integration guide →The native API every iOS package here calls into: authorization, queries, background delivery.
• HealthKit data types by group →Apple's identifiers grouped the way Apple groups them — check the type you need exists before blaming the bridge.
• Every HealthKit error code →What the HKError a bridge passes through actually means.
• 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-health vs @kingstinct/react-native-healthkit: side by side →

• @kingstinct/react-native-healthkit16.0.0 · 2026-09-18Apple HealthKit, on iOS.
• react-native-health-connect4.1.3 · 2026-08-06Android Health Connect.
• 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 work on Android?

No. Its README describes it as a package for Apple HealthKit on iOS, and HealthKit does not exist on Android. React Native apps that also ship on Android usually pair it with react-native-health-connect, whose own README lists react-native-health as the iOS counterpart.

Can I use react-native-health with Expo?

Not in Expo Go. The README says the package is not available in the Expo Go app and points to custom development clients instead, so you need a development build that compiles the native module in.

Which Info.plist keys does react-native-health need?

The README lists NSHealthShareUsageDescription and NSHealthUpdateUsageDescription, plus NSHealthClinicalHealthRecordsShareUsageDescription only if you request clinical records. It also asks you to add the HealthKit capability to the target in Xcode, and to tick Clinical Health Records there if you use clinical types.