When something goes wrong, you may see one of these error codes or messages on your watchface. This page explains what each one means and how to fix it.
Click an error to jump to its fix:
Garmin Communications API Errors:
Message: "Failed to authenticate" or "Auth Failed"
Cause: Your Dexcom Share credentials are incorrect or the wrong region is selected.
Solution:
Message: "Maximum authentication attempts exceeded"
Cause: Too many failed logins in a short time.
Solution:
Message: "Session ID not found"
Cause: Your session has expired or was never created.
Solution:
Message: "Session not active or timed out"
Cause: Your Dexcom Share session has expired (typically after 24 hours).
Solution:
Message: "Username must be non-empty string"
Cause: No username in the settings.
Solution:
Message: "Password must be non-empty string"
Cause: No password in the settings.
Solution:
Message: "No current glucose reading available"
Cause: Dexcom sent no recent glucose data. This usually means:
Solution:
Message: "Invalid or malformed JSON in server response"
Cause: The Dexcom server sent an unexpected or broken response.
Solution:
Message: "Unknown error code in server response"
Cause: The Dexcom API sent an error code the app doesn't know.
Solution:
Message: "Unexpected server response"
Cause: The Dexcom server responded in an unexpected way.
Solution:
These errors come from the Garmin Communications API, when the watch has network, Bluetooth or communication problems.
Click an error to jump to its fix:
Code: UNKNOWN_ERROR
Cause: An unknown error.
Solution: Restart your watch and check the connection.
Code: BLE_ERROR
Cause: A general Bluetooth error.
Solution:
Code: BLE_HOST_TIMEOUT
Cause: Timed out waiting for a response from the host (phone).
Solution:
Code: BLE_SERVER_TIMEOUT
Cause: Timed out waiting for a response from a server.
Solution:
Code: BLE_NO_DATA
Cause: The response had no data.
Solution: Wait for the next update. Check that the Dexcom app has readings.
Code: BLE_REQUEST_CANCELLED
Cause: The request was cancelled by the system.
Solution: This is normal. The app tries again by itself.
Code: BLE_QUEUE_FULL
Cause: Too many requests have been made.
Solution:
Code: BLE_REQUEST_TOO_LARGE
Cause: The request data was too large.
Solution: Contact me. This is an app issue.
Code: BLE_UNKNOWN_SEND_ERROR
Cause: Send failed for an unknown reason.
Solution:
Code: BLE_CONNECTION_UNAVAILABLE
Cause: No BLE connection is available.
Solution:
Code: INVALID_HTTP_HEADER_FIELDS_IN_REQUEST
Cause: The request had invalid HTTP header fields.
Solution: Contact me. This is an app configuration issue.
Code: INVALID_HTTP_BODY_IN_REQUEST
Cause: The request had an invalid HTTP body.
Solution: Contact me. This is an app issue.
Code: INVALID_HTTP_METHOD_IN_REQUEST
Cause: The request used an invalid HTTP method.
Solution: Contact me. This is an app issue.
Code: NETWORK_REQUEST_TIMED_OUT
Cause: The request timed out before a response came in.
Solution:
Code: INVALID_HTTP_BODY_IN_NETWORK_RESPONSE
Cause: The response from the server could not be read.
Solution:
Code: INVALID_HTTP_HEADER_FIELDS_IN_NETWORK_RESPONSE
Cause: The response from the server had invalid header fields.
Solution:
Code: NETWORK_RESPONSE_TOO_LARGE
Cause: The response was too large for your watch.
Solution:
Code: NETWORK_RESPONSE_OUT_OF_MEMORY
Cause: Your watch ran out of memory while reading the response.
Solution:
Code: STORAGE_FULL
Cause: The watch storage is too full to store the response.
Solution:
Code: SECURE_CONNECTION_REQUIRED
Cause: The address must start with https://.
Solution:
Code: UNSUPPORTED_CONTENT_TYPE_IN_RESPONSE
Cause: The server sent something the app did not expect, for example a web page instead of data.
Solution:
Code: REQUEST_CANCELLED
Cause: Your watch cancelled the request.
Solution:
Code: REQUEST_CONNECTION_DROPPED
Cause: The connection was lost before a response came in.
Solution:
Meaning: No data available or app not configured.
Solution:
Meaning: The last reading is more than 10 minutes old.
Solution:
More help: See the FAQ or go back to the Introduction.