Clarification on HealthKit Observer Behavior in Flutter App vs Native iOS App

Question

Created 1w

Replies 2

Boosts 0

Participants 3

Hello Apple Developer Support / Community,

I would like clarification regarding HealthKit observer behavior when comparing a Flutter-based iOS app with a fully native iOS app.

We are using HealthKit background delivery with:

HKObserverQuery
enableBackgroundDelivery
HKAnchoredObjectQuery

We have observed that in a Flutter-based app, HKObserverQuery callbacks appear to execute multiple times or more frequently than expected for a single data update. In comparison, a native iOS implementation using similar HealthKit logic appears more stable and predictable.

We would like to understand the expected platform behavior and whether there are any known considerations from Apple’s perspective.

Specific questions:

Does iOS treat HealthKit observer delivery differently for apps built with Flutter versus fully native UIKit / Swift apps?
Are there known issues where app lifecycle handling, Flutter engine initialization, method channels, isolates, or plugin architecture could cause repeated observer callbacks?
Can repeated HKObserverQuery executions occur if queries are registered multiple times during app launches or engine restarts?
Does Apple recommend any specific observer management pattern for cross-platform frameworks such as Flutter?
From the HealthKit system side, should observer callback frequency be identical regardless of whether the app is Flutter or native, assuming the same iOS code is used?

We are trying to determine whether this behavior is due to HealthKit delivery semantics, duplicate observer registration, Flutter lifecycle integration, or framework-related limitations.

Any guidance from Apple or developers who have implemented HealthKit successfully in Flutter would be appreciated.

Thank you.

Answered by DTS Engineer in 887129022

I know very little about Flutter and can't comment on that, but would like to be clear that, when using HKObserverQuery + enableBackgroundDelivery, the update handler of HKObserverQuery should be triggered when the device's Health store data it's observing changes. If the app is suspended at that time and has background execution budget, the system should wake it up and run the update handler. Whether the app is built with Flutter or not doesn't matter to HealthKit.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

Boost

Answer 1

DTS Engineer OP

Apple

1w

Thank you for reaching out with this detailed post. I do not have any experience with the 3rd party tool you describe and I would suggest to contact their support channel.

For what I can see the native objects get eventually called so HealthKit does not distinguish between a 3rd party development and a native iOS development. At the operating system level, a compiled 3rd party app is simply a standard iOS executable running from a third party. Therefore, any discrepancies in HKObserverQuery behavior are almost certainly rooted in how the 3rd party engine, the app lifecycle, and the specific HealthKit plugin manage query registrations and background execution.

HealthKit determines background delivery based on the app's bundle identifier, entitlements, background modes. The OS has no awareness of the 3rd party framework as that framework still calls the same objects? HealthKit allows you to register multiple observer queries for the same data type.

Hope other developers have experience with that third party development and I still think you should consider their support channel to get answers to your questions.

Albert   Worldwide Developer Relations.

1

Answer 2

DTS Engineer OP

Apple

5d

Accepted Answer

I know very little about Flutter and can't comment on that, but would like to be clear that, when using HKObserverQuery + enableBackgroundDelivery, the update handler of HKObserverQuery should be triggered when the device's Health store data it's observing changes. If the app is suspended at that time and has background execution budget, the system should wake it up and run the update handler. Whether the app is built with Flutter or not doesn't matter to HealthKit.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

2