Validic incident
Newest Legacy iOS Native SDK versions for Apple Health summary query optimization
Validic experienced a notice incident on October 17, 2025 affecting Legacy SDK (1.x.x), lasting 16d 21h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 17, 2025, 05:07 PM UTC
This is less of reporting an issue and more for noting a fix for something Validic noticed about Apple iOS 26 and summary records. Apple has always surfaced old summary records as new records in their HealthKit api as part of their housekeeping. In iOS 26, it appears this can happen much more frequently. Apple has acknowledged this is a bug in iOS 26. In versions older than Legacy iOS Native 1.18.0, in certain situations, the SDK would process that old record and then query every summary record since then. This creates a large volume of redundant summary records and slows the speed at which new data is ingested for users. More information about this is on this KBA: https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements Clients using the Apple Health/HealthKit module in the Validic SDK are encouraged to update to Legacy iOS Native 1.18.0 to mitigate this and have the best performance they can with our integration with the HealthKit API If you or your team has any questions about the information above or in the linked KBA, open a ticket with Validic technical support by emailing [email protected]
- resolved Nov 03, 2025, 02:49 PM UTC
We are going to close this status page as it was more of an FYI for our clients than reporting an internal issue. If there are any questions about the below KBA, then reach out to the technical support team at [email protected] https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements