Normalize timestamps by stripping time zone offsets from Health data #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a minimal, backwards-compatible patch to normalize Apple Health timestamps by stripping time zone offsets. It ensures compatibility with SQL
TIMESTAMP WITHOUT TIME ZONE
fields and resolves import issues on newer iOS exports (e.g., June 2025).Changes
_strip_tz()
helper inparse.py
to cleancreationDate
,startDate
, andendDate
valuesparse.py
to use the helper in the default record streamActivitySummaryFormatter
andSleepAnalysisFormatter
informatters.py
to apply the same normalizationMotivation
iOS-exported data may include time zone offsets (e.g.,
+0100
), which are incompatible with the current database schema. This fix ensures consistent ingestion across older and newer data sets.