Most ZenSugarX troubleshooting becomes simple once you know whether this iPhone is collecting directly from a compatible sensor or following an existing Nightscout timeline.
Use the compatible-sensor workflow when this iPhone is the device collecting the sensor data. Confirm Bluetooth permission, the selected sensor, recent readings and history recovery before investigating downstream surfaces.
Use Follower when another source already publishes the authoritative timeline to Nightscout. Confirm the server first, then compare the newest server timestamp with the newest ZenSugarX timestamp.
The Watch app and complication display state delivered by ZenSugarX. They do not measure glucose. If the Watch view is stale, verify the iPhone data first, then the Watch app installation, pairing and complication freshness.
A small Lock Screen widget and the full-width Live Activity are different Apple surfaces. Live Activity is the intended fast-glance surface; a widget timeline may refresh less frequently under iOS scheduling.
Check Nightscout or the sensor source, then the ZenSugarX local history, then the chart. A server point that is missing locally is a synchronization/backfill problem; a local point that is missing visually is a rendering problem. This separation prevents guessing.
Include the device, ZenSugarX version/build, data-source mode, approximate time of the problem and whether the authoritative Nightscout/sensor history is complete. Do not send passwords, private keys or full Nightscout credentials.
Development software. ZenSugar is not a validated medical device and must not be the sole basis for insulin dosing or emergency decisions. Verify important readings using the methods recommended by your device manufacturer and healthcare team.
