You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The watchface of Trios Apple Watch App was reported to take too long to have the user confirm the bolus. In some cases this leads to a forgotten bolus because it took too long for a kid to wait for that. It might relate to a huge Apple Health database, at least this was braught together here.
Attach a Log
To Reproduce
Expected behavior
Watchface should get a timeout after which an info-box informs the user to deliver Bolus with trio app instead of watch.
Screenshots
Setup Information (please complete the following information):
Smartphone:
Hardware: iPhone SE + AW Series 3
OS Version: [e.g. iOS 17.5]
Pump:
Manufacturer: [e.g. Insulet]
Model: [e.g. Omnipod Dash or Eros]
CGM:
Device: [e.g. Dexcom G7]
Manager app: [e.g. Dexcom App or xDrip4iOS]
Trio Version:
Version Number: [e.g. 1.9.2]
Repo: nightscout/trio
Git Reference: [e.g. commit hash]
Technical Details
If applicable, provide any technical details that might help in diagnosing the problem. This could include logs, error messages, or relevant configuration details.
Additional context
Might need some code review...
The text was updated successfully, but these errors were encountered:
Describe the bug
The watchface of Trios Apple Watch App was reported to take too long to have the user confirm the bolus. In some cases this leads to a forgotten bolus because it took too long for a kid to wait for that. It might relate to a huge Apple Health database, at least this was braught together here.
Attach a Log
To Reproduce
Expected behavior
Watchface should get a timeout after which an info-box informs the user to deliver Bolus with trio app instead of watch.
Screenshots
Setup Information (please complete the following information):
Smartphone:
Pump:
CGM:
Trio Version:
Technical Details
If applicable, provide any technical details that might help in diagnosing the problem. This could include logs, error messages, or relevant configuration details.
Additional context
Might need some code review...
The text was updated successfully, but these errors were encountered: