health_kit_reporter
Dart · pub.dev: health_kit_reporter · latest 2.3.1 (2024-12-12) · registry read 2026-10-03
What it wraps
Apple HealthKit on iOS, through the HealthKitReporter CocoaPods library. Its pubspec declares iOS as the only plugin platform.
“iOS only usage, since AppleHealth is not available on Android devices.”
Source: README
Named in the registry description: Apple HealthKit.
Install
Registry and repository facts
Read from pub.dev 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
- pub.dev: health_kit_reporter
- Latest version
- 2.3.1, published 2024-12-12660 days before our 2026-10-03 read
- First published
- 2020-11-20 · 30 versions published
- Licence
- MITpub.dev tags: license:mit
- Platforms
- iOSpubspec flutter.plugin.platforms: ios
- Requires
- sdk >=2.12.0 <4.0.0 · flutter >=1.20.0pubspec environment
- Repository
- kvs-coder/health_kit_reporter
- Last commit, default branch
- 2024-12-12660 days before our 2026-10-03 read · read by git on 2026-10-03
- GitHub signals
- 37 stars · 33 open issues and PRs · not archived · last push to any branch 2024-12-12GitHub API, read 2026-10-03
Registry description: “Helps to write or read data from Apple Health via HealthKit framework.”
What the README warns about
Each item is the project’s own statement, checked on 2026-10-03, quoted where the wording matters.
README and registry disagree. The default-branch README tells you to depend on
health_kit_reporter: ^3.1.0and to point the HealthKitReporter pod at a fork'sfeature_add_clinical_recordsbranch until an upstream pull request is merged. pub.dev's latest version at our read was 2.3.1, and its package page showed a^2.3.1dependency.Source: README and pub.dev package page
Workout routes need location permission. The README asks for the two CoreLocation usage strings if you use workout route series.
Source: README
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.
- HealthKit permission builder →The Info.plist keys and read/share sets any HealthKit plugin needs.
Other Flutter packages on this list
Flutter health data packages: every package side by side, and how to choose →
- health13.3.2 · 2026-08-14Apple Health (HealthKit) on iOS and Google Health Connect on Android, per the README and the platforms its pubspec declares.
- health_connector3.11.1 · 2026-09-16Apple HealthKit on iOS and Android Health Connect.
- flutter_health_connect1.2.3 · 2023-03-08Android Health Connect.
Questions
- Does health_kit_reporter work on Android?
- No. Its README says it is for iOS only because Apple Health is not available on Android devices, and its pubspec declares iOS as the only plugin platform. For Flutter apps that need both stores, the cross-platform packages listed here are health and health_connector.
- Why does the health_kit_reporter README mention version 3.1.0?
- Because the README on the repository's default branch is ahead of pub.dev. At our 2026-10-03 read it documented a 3.1.0 dependency and a temporary Podfile override, while the latest version published on pub.dev was 2.3.1. The pub.dev page shows the README for the published version.
Registry facts read by scripts/fetch-libraries.mjs on 2026-10-03 and refreshed weekly; the latest release was published 660 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.