Gideon Zenz b5b0b585cc Fix #5797: Advance HC sync cursor by last-written record timestamp ...

The sync state cursor was advancing to the slice end timestamp
unconditionally, even when no records were written. Late-arriving data
(sleep, workouts, VO2Max, etc.) that arrives after the cursor has
already advanced past it would be permanently skipped.
Each syncer now reports the latest timestamp of records actually
inserted into Health Connect. The sync cursor advances to
max(currentPersisted, latestRecordTimestamp) instead of
sliceEndTimestamp. If no records were written for a slice, the cursor
stays put. This handles all late-arriving data generically without
needing per-data-type special-casing.

2026-03-02 20:19:02 +01:00

..

src

Fix #5797: Advance HC sync cursor by last-written record timestamp

2026-03-02 20:19:02 +01:00

build.gradle

Update protobuf to v4.34.0

2026-03-02 20:06:04 +01:00

lint-baseline.xml

Update linter baseline

2024-02-19 12:14:36 +01:00

proguard-rules.pro

Add re2j to proguard rules

2026-01-03 14:30:16 +01:00