Common user problems and misconceptions

Outdated Application Versions
A significant number of support queries stem from users operating on outdated versions of the app. This often leads to unexpected behavior or missing features. Users are sometimes unaware of the correct process to update their application via TestFlight (iOS) or OneDrive (Android), resulting in them not having the latest build.

Android Installation Issues
On Android, users frequently encounter installation problems because they haven't enabled the setting to allow installation from unknown sources. Although this requirement is documented in the Notion guide, many users overlook it during the installation process.

Glucose Log Editing Constraints
Some users report being unable to edit glucose logs for previous dates. This leads them to raise support tickets under the assumption that it's a bug, when in fact, it's the intended behavior or a known limitation.

Glucose Tracker UI Expectations
When navigating to the glucose tracker from the home page, users see four entry boxes labeled Fasting, Breakfast, Lunch, and Dinner. Users often expect these values to be auto-filled using data from their Continuous Glucose Monitor (CGM), rather than requiring manual input, leading to confusion and feature requests.

Dashboard Visibility Confusion
Users sometimes express concern that they cannot view the same dashboard or metrics that their coach sees. This results in misunderstandings or the incorrect assumption that there's a bug or data-syncing issue.

Sandbox vs. Production Environment Confusion
Occasionally, users get confused between the sandbox and production environments. This can lead to issues such as logging in to the wrong version of the app, misinterpreting data, or thinking that expected updates haven't been applied.