onsim 온심

Problem

readRecords returns at most 1,000 records per call and only the first page was read. For sources like Samsung Health that split heart rate finely, the most recent part of the weekly window was cut off entirely (a real 4-minute sensor gap showed as 17 minutes unmeasured).

Solution

Replaced with a readAllRecords that walks every pageToken and shipped a one-time purge migration for already-polluted caches.

Problem

iOS native reads swallowed failures as empty arrays, so an app revived in the background on a locked device received zero records for every type and yesterday's workouts vanished for the rest of the process.

Solution

Errors now propagate to Dart, and zero-record responses while not in the foreground are never accepted as authoritative — a second line of defence.

Problem

An auto-launch loop where phone and watch woke each other endlessly, a 25-second scene-watchdog SIGKILL from leftover HealthKit background delivery, a 32-bit Int trap at launch and NSNull payload crashes had accumulated.

Solution

Introduced liveness heartbeats, stale-command rejection, AOD elapsed-time handling and ghost-session rescue, locked down in an 840-line design doc. The same design was ported to Wear OS with three-source HR arbitration.

Problem

Android workout-history loading, cold start, landing repaint and idle heat were driving user complaints.

Solution

Diagnosed and fixed step by step — Dart → pipeline → native → shared glass snapshots → decorative animation policy → stopping frame generation when idle — and documented why RepaintBoundary alone could not solve it.

Problem

Social and ranking features caused Firestore read costs to spike.

Solution

Functions-side caching, ranking debounce, single client listener and a persistent cache, applied in sequence with a read-audit document as evidence.

Problem

Sensitive data such as sleep and menstrual records were silently back-filled, uids could surface on social screens, and a mis-classified dev build once deleted real accounts.

Solution

Moved to explicit consent for everyone with a SensitiveConsentManager that blocks collection of unconsented types, introduced publicId across all social surfaces, encrypted every local cache and added a one-hour guard on account deletion.

Problem

A Sign in with Apple name re-entry issue (guideline 2.5.4, ITMS-90683) and a prod-merge routine that collided with a never-empty review window.

Solution

Fixed at the root via displayName preservation → name cache → confirmation step → SIWA revoke. Switched to v{version} branches as release endpoints and moved the build-number source of truth to TestFlight.