Is react-native-google-fit deprecated?

The package itself carried no deprecation message on npm at our last check, but the API under it is deprecated: its README says Google has deprecated the Google Fit API and is transitioning to Health Connect, and Google's Fit migration guide says the API will only be supported until the end of 2026.

Why does react-native-google-fit return Authorization Failed?

The README's troubleshooting section lists three causes: the SHA-1 certificate fingerprint does not match the one registered in Google Cloud Console, the package name is wrong, or the test user's email is missing from the OAuth consent screen.

What replaces react-native-google-fit for new Android work?

Google's Fit migration guide recommends Health Connect for step tracking and mobile-first apps, and the Google Health API for cloud-based integrations. In React Native, Health Connect is reached through react-native-health-connect or one of the cross-platform Capacitor and Flutter plugins listed on this site.

React Native library

react-native-google-fit

JavaScript · npm: react-native-google-fit · latest 0.22.1 (2025-10-08) · registry read 2026-10-03

react-native-google-fit is a React Native bridge to the Google Fit API on Android. Its README acknowledges that Google has deprecated the Google Fit API in favour of Health Connect and says the maintainers will support the library while the API remains accessible. Google's Fit migration guide says the Google Fit API will only be supported until the end of 2026 and recommends Health Connect for step tracking and mobile-first apps.

What it wraps

The 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.
“A React Native bridge module for interacting with Google Fit on Android.”
Source: README

Named in the registry description: Google Fit.

Install

Expo

npx expo install react-native-google-fit

From the README

React Native CLI

npm install react-native-google-fit --save

From the README

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-google-fit
Latest version: 0.22.1, published 2025-10-08360 days before our 2026-10-03 read
First published: 2017-01-12 · 72 versions published
Licence: MITpackage.json license
Platforms: not stated in registry metadata
Requires: expo * · react-native >=0.60.0package.json peerDependencies
Repository: StasDoskalenko/react-native-google-fit
Last commit, default branch: 2026-10-021 day before our 2026-10-03 read · read by git on 2026-10-03
GitHub signals: 372 stars · 9 open issues and PRs · not archived · last push to any branch 2026-10-02GitHub API, read 2026-10-03

Registry description: “A React Native bridge module for interacting with Google Fit”

What the README warns about

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

The README's own notice about the platform underneath it.
“Google has deprecated the Google Fit API and is transitioning to Health Connect. While the Google Fit API remains available, we are committed to maintaining this library and bringing it up to the latest standards.”
Source: README
Google's date. The Fit migration guide says the Google Fit API, including the REST API, will only be supported until the end of 2026, and recommends Health Connect for step tracking and mobile-first apps.
“The Google Fit API (including the REST API) will only be supported until the end of 2026.”
Source: Google's Fit migration guide (last updated 2026-09-10)
"Authorization Failed". The README's troubleshooting section says to check that the SHA-1 certificate matches the one in Google Cloud Console, that the package name is correct, and that the test user's email is added to the OAuth consent screen.
Source: README

The API underneath

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

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.
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.

Questions

Is react-native-google-fit deprecated?: The package itself carried no deprecation message on npm at our last check, but the API under it is deprecated: its README says Google has deprecated the Google Fit API and is transitioning to Health Connect, and Google's Fit migration guide says the API will only be supported until the end of 2026.
Why does react-native-google-fit return Authorization Failed?: The README's troubleshooting section lists three causes: the SHA-1 certificate fingerprint does not match the one registered in Google Cloud Console, the package name is wrong, or the test user's email is missing from the OAuth consent screen.
What replaces react-native-google-fit for new Android work?: Google's Fit migration guide recommends Health Connect for step tracking and mobile-first apps, and the Google Health API for cloud-based integrations. In React Native, Health Connect is reached through react-native-health-connect or one of the cross-platform Capacitor and Flutter plugins listed on this site.

Registry facts read by scripts/fetch-libraries.mjs on 2026-10-03 and refreshed weekly; the latest release was published 360 days before our 2026-10-03 read. README quotes identify the project’s own statements; the selection, grouping and comparisons are AIFitnessAPI’s. For tagged releases of the main bridges, see the SDK release tracker.

← All health and fitness libraries