This incident has been resolved.
Apr 7, 13:59 EDT
The update has been deployed to production and we are currently monitoring to confirm that everything is working as expected.
Apr 1, 11:17 EDT
Validic has identified the fix for this issue and we are planning to deploy it to production in the morning hours (US Eastern Time) on Wednesday, April 1, 2020.
This status will continue to be updated.
Mar 31, 17:31 EDT
We have discovered an issue with this fix that was causing anyone using a version of the Validic Mobile SDK older than 1.12 to see zero steps for Apple Health users. Therefore we are rolling back this change and will work on a different solution.
We will post updates related to this issue here as they become available.
Mar 30, 13:28 EDT
This change was rolled out on Friday, March 27 and we are monitoring the results of the change.
Mar 30, 09:47 EDT
We have identified a resolution to the duplicate steps issue affecting Validic iOS Mobile SDK v1.12.0. This fix is planned to be released by the end of this week. The total number of steps will then equal the sum of origin=unknown, origin=device, and origin=manual.
Origin=unknown steps will no longer duplicate steps that are already counted in origin=device and origin=manual. The updated SDK versions are now back on the mobile portal and we encourage you to update to the newest frameworks for production use as soon as Monday, March 30.
Mar 24, 16:39 EDT
Please be advised that the iOS Validic Mobile SDK version 1.12.0 may cause technical issues with Healthkit steps reporting in the Inform API. Steps values may be inadvertently doubled if you are summing all Inform summaries steps values; origin=unknown for the HealthKit SDK represents the total number of steps (the sum of origin=device and origin=manual). In this version of the SDK, you should only use origin=device and origin=manual, and ignore origin=unknown.
This issue impacts the following SDK versions:
- iOS Full Library R1.12.0 - released February 3, 2020
- iOS Aggregator Library R1.12.0 - released February 3, 2020
The affected SDK versions have been removed from the mobile portal. If you have already added this SDK version to your mobile project, please revert to version 1.11.5 which is available on the mobile portal or adjust your processing for steps values.
We will update this status as new information is available for this issue.
Mar 11, 15:42 EDT