expo-health-connect (deprecated)

Migration commands

npm uninstall expo-health-connect

npx expo prebuild --clean

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: expo-health-connect

Latest version

0.1.1, published 2024-07-31794 days before our 2026-10-03 read

First published

2024-06-30 · 2 versions published

Licence

MITpackage.json license

Platforms

not stated in registry metadata

Requires

expo * · react * · react-native *package.json peerDependencies

Deprecated

Merged into react-native-health-connect v4 — remove this package, replace the expo-health-connect entry in your app.json plugins array with react-native-health-connect, then re-run expo prebuild --clean. See https://github.com/matinzd/react-native-health-connectnpm deprecation message on the latest version

Repository

matinzd/expo-health-connect

Last commit, default branch

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

GitHub signals

15 stars · 1 open issues and PRs · archived · last push to any branch 2026-08-01GitHub API, read 2026-10-03

Registry description: “Expo config plugin for react-native-health-connect”

What the README warns about

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

• The npm deprecation message, verbatim from the registry: "Merged into react-native-health-connect v4 — remove this package, replace the expo-health-connect entry in your app.json plugins array with react-native-health-connect, then re-run expo prebuild --clean. See https://github.com/matinzd/react-native-health-connect"

  Source: npm registry

• The duplicate-class failure. The README says that with react-native-health-connect v4 installed, keeping this package makes the Android build fail because both contribute the Kotlin class expo.modules.healthconnect.HealthConnectPackage. Removing this one resolves it.

  Source: README

• Issues go elsewhere now. The README says the repository no longer accepts contributions and asks for issues and pull requests on react-native-health-connect.

  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 →What the merged package configures for you: permissions and the rationale activity.
• Health Connect returns no data →If reads come back empty after the migration.

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.
• react-native-health-connect4.1.3 · 2026-08-06Android Health Connect.
• 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

How do I fix the duplicate expo.modules.healthconnect.HealthConnectPackage build error?

Uninstall expo-health-connect. Both it and react-native-health-connect v4 contribute that same Kotlin class, so the Android build fails while both are installed. The README's steps are: npm uninstall expo-health-connect, replace expo-health-connect with react-native-health-connect in the app.json plugins array, then run npx expo prebuild --clean.

Is expo-health-connect still maintained?

No. The npm registry marks it deprecated, and the README says the repository is archived and no longer accepts contributions. Its functionality lives on inside react-native-health-connect from v4, where issues should now be filed.