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
I receive the notification that LF is no longer running.
It seems to have crashed. Sometimes, I can see that NS data is not fully updated from iAPS/Trio phone. and LF will crash shortly after launch, ie. while appearing to fetch BG values.
I saw some mention of hardening of Dexcom Share.
Are there logs or data I can provide to help diagnose ?
The text was updated successfully, but these errors were encountered:
Hi, I am currently re-writing the Trio part of LoopFollow. I hope it will soon be on dev so you can grab it from there. Any chance you could have LoopFollow running on your mac and get the exception from there - then it will be very clear where it crashes.
On version 2.2.4 (and earlier)
I receive the notification that LF is no longer running.
It seems to have crashed. Sometimes, I can see that NS data is not fully updated from iAPS/Trio phone. and LF will crash shortly after launch, ie. while appearing to fetch BG values.
I saw some mention of hardening of Dexcom Share.
Are there logs or data I can provide to help diagnose ?
The text was updated successfully, but these errors were encountered: