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
If a user enters carbs, and then decided to edit carb hours there is a possibility that Loop hangs.
Example: User enters 10 g of carbs with 180 minutes absorption time, and then decides to change this to 240 by edit manually the number is added to the existing number if the user doesn't delete the previous number. This will then be saved as "180240" absorption time. After save, Loop seems to work fine, but the long absorption time will cause Loop to hang - not communicating with Rileylink, no new BG number is captures, and the phone is slow. After 20 minutes the user will get a Loop has failed warning. Restarting the app makes the GUI strange - the graphs and Nightscout is strange due to that Loop has calculated numbers far into the future it seems.
Even if the user noticed that the number was wrongly saved, Loop seems to lock up if the user changes absorption time back to 240. Have to force close Loop and restart.
Solution: There should be a max number for carbs absorption time (for example 999).
The text was updated successfully, but these errors were encountered:
I have seen this before and experienced the same symptoms. It doesn't seem to crash with only 3 characters in my testing so I think we should limit the text field to 3 characters. This provides 16.65 hours of possible carb absorption (should be more than long enough for everyone).
If a user enters carbs, and then decided to edit carb hours there is a possibility that Loop hangs.
Example: User enters 10 g of carbs with 180 minutes absorption time, and then decides to change this to 240 by edit manually the number is added to the existing number if the user doesn't delete the previous number. This will then be saved as "180240" absorption time. After save, Loop seems to work fine, but the long absorption time will cause Loop to hang - not communicating with Rileylink, no new BG number is captures, and the phone is slow. After 20 minutes the user will get a Loop has failed warning. Restarting the app makes the GUI strange - the graphs and Nightscout is strange due to that Loop has calculated numbers far into the future it seems.
Even if the user noticed that the number was wrongly saved, Loop seems to lock up if the user changes absorption time back to 240. Have to force close Loop and restart.
Solution: There should be a max number for carbs absorption time (for example 999).
The text was updated successfully, but these errors were encountered: