Features & Bugs

Error occurring on app load after v1.2.0

If I inject at 0709, it won't show as 0709 but 0700 (on the top of the hour).

I have noticed the recent update (1.2.0) where basal and bolus data is pulled across (I am using libre 2 and Librelink to pull the data), in the morning it doesn't pull across the bolus, just the basal, so I manually add in the bolus.

When using Libre (via NovoPen) for insulin, I cannot amend the times inside the Enhance-d app after they have synchronised. I have tried to change the data (I can) but when I click save, it doesn't save the amended information.

Change the way the Time in Range during exercise is calculated to consider event duration.

We're investigating an issue affecting Apple Health users when trying to add this integration to the app. Some Apple health users are met with a loading screen for several minutes after clicking Connect whilst the integration connects. We're also aware that after integrating, new data may not be being synced going forward. We're sorry for the inconvenience and we're looking into the issue and hope to be able to issue a fix within the next few releases.

We have been made aware of a small number of users experiencing data sync issues from Freestyle Libre integration. We're investigating the issue and hope to have an update and resolution in the coming days. We're extremely sorry for the inconvenience this may be causing you and are working hard to resolve this as quickly as possible.

Wahoo integration is not considering the UTC offset. Started an activity at 17:47 shows as 16:47. As such the glucose value is out by a user's UTC offset relative to the activity. E.g. occuring 1 hour ahead of actual value relative to the session if the session took part in UTC+1

We've noticed that during the onboarding process you are required to scroll down on certain pages to find the skip or next buttons. This particularly affected users with smaller resolution displays. We're placing the next buttons into a handy sticky bottom bar so that they're always visable on screen during the onboarding process, which should help make onboarding as slick and easy to complete as possible.

There appears to be an issue with nightscout API which can cause it to Authenticate and appear as if it has integrate successfully, whilst failing silently. The integration then shows as not yet integrated on the integrations page.