---
title: "Apple Health Summary Record Volume Improvements"
canonical: "https://help.validic.com/space/VCS/4957044737/Apple%20Health%20Summary%20Record%20Volume%20Improvements"
format: markdown
---
## **Overview**

With iOS Inform Native SDK 2.1.0 and iOS Legacy Native 1.18.0, Validic implemented improvements to how the SDK handles “old sample updates” reported by Apple Health (HealthKit). These changes significantly reduce excessive or duplicate *summary record* submissions that some clients observed before this release.

This enhancement does **not** change how Apple Health itself behaves, but it improves how the SDK interprets and responds to HealthKit’s background updates.

---

## **Background**

Apple Health (HealthKit) occasionally reprocesses older samples during internal maintenance.  
 When this happens, HealthKit generates a “new sample” event — even though the underlying record hasn’t actually changed. This is intentional Apple behavior.

In iOS 26, Apple introduced a regression that caused some of these “old sample updates” to occur more frequently. As a result, iOS Native SDK versions < 2.1.0 Inform and < 1.18.0 Legacy could reprocess large ranges of data unnecessarily.

---

## **What Changed in iOS Inform Native SDK 2.1.0**

In earlier iOS Native SDK versions (< 2.1.0 Inform and < 1.18.0 Legacy):

- A HealthKit “update” notification for an old sample (for example, from 2022) could cause the SDK to re-query and recreate all summary data from that old date to the present day.
- This resulted in hundreds of redundant summary records per user, often inflating record volume and causing spikes in system metrics.

In iOS Native Inform SDK 2.1.0+ Inform and 1.18.0+ Legacy:

- The SDK now limits the scope of HealthKit reprocessing.
- When HealthKit reports an update for a sample from a past date, the SDK only reprocesses that specific day’s summary instead of the entire date range.
- This prevents the unnecessary creation of multiple daily summary records for the same data, dramatically reducing noise and load.

## **Note about expectations with upgrade to 2.1.0+ Inform and 1.18.0+ Legacy**

The Apple Health queue is on the local device, and after updating the app, you may notice that there are a lot of summary records coming through with the old SDK version. This is due to the queue clearing from the old summary records. Once that queue has cleared, you will see the updated SDK version coming through on new records in the user’s local queue. 

NOTE: iOS Native Inform 2.1.2 was released to address the long local queue on the user’s phone. Clients should update to >= 2.1.2 to avoid the frustration of ancient summary records continuing to be synced to our server [https://help.validic.com/space/VRN/blog/5025300496/Inform+Mobile+SDK+(v2.x)+Release+Notes+-+11122025#iOS-Native-Inform-Libraries-Release](https://help.validic.com/space/VRN/blog/5025300496/Inform+Mobile+SDK+(v2.x)+Release+Notes+-+11122025#iOS-Native-Inform-Libraries-Release) 

## **Questions?**

Reach out to Validic technical support if you have any questions about how to access the Inform SDK that has the 2.1.0 iOS Inform Native SDK, or if you have any questions around this change.