Trio bloats Apple Health

[DreyCon-Raphael]

Describe the bug

Using Trio and enabling pushing data to Apple Health (AH) results in rapidly increasing AH entries exceeding GB (within few days). Discussion on Discord: (HERE)

Attach a Log

To Reproduce

1. enable Trio to write to AH
2. wait a couple of days
3. control size of AH, see GB of data

Expected behavior

less size in entries, no so granular (every single smb gets logged, maybe also BG that already might get logged by another app)

Screenshots

Setup Information (please complete the following information):

Smartphone:

• Hardware: iPhone 15 Pro, but might be on all others, too
• OS Version: 17.5, but might be on all others, too

Pump:

• Manufacturer: Insulet
• Model: Omnipod DASH, but might be on all others, too

CGM:

• Device: Dexcom G7, but might be on all others, too
• Manager app: Dexcom App, but might be on all others, too

Trio Version:

• Version Number: 0.1.0
• Repo: nightscout/trio
• Git Reference: Branch: dev dff37ac

Technical Details

Additional context

Might impact communication speed between cellphone and watch. Some report time extremely increases waiting for watch face to permit calculated bolus. See this issue.

[dnzxy]

This is a known issue and will have to be addressed by basically rewriting the entire AH layer in Trio. Thank you for reporting it; it is a known issue.

A personal side note: if you do not require AH to run, I would suggest you turn it off when using an oref-running app on iOS, because they all suffer from this issue currently.