Tidepool keeps on disconnecting on unreliable networks

[michaelcadilhac]

I'm traveling through France, and every now and then I get disconnected from mobile network. When connection is restored, I'm disconnected from tidepool, which is annoying because the log in page just randomly shows up when using the phone.

Version: 805ba04-2026.03.01 Code: 2126030111

Data Source: G7

Related/unrelated: I have to reset the Dexcom Transmitter ID fairly often (erase, rewrite) for xdrip to reconnect to it. It seems related because it happens at these unreliable network points, but may be a coincidence.

[Navid200]

I disconnect from the internet every now and then.
When that happens, I never see any of those logs you are showing related to Tidepool in xDrip. And the next time I reconnect, Tidepool syncs.

Are you sure you are connected and logged into Tidepool properly?
There is an option to verify I think on the Tidepool menu in xDrip.

[ahaarrestad]

Thanks both — I dug into the log and can confirm the mechanism.

When the access token happens to need refreshing at the same moment the network is flaky, xDrip'''s silent token refresh (via AppAuth) fails with a transient NETWORK_ERROR — that'''s the {"type":0,"code":3} line in your screenshot. The code currently treats any refresh failure the same way and falls back to a full interactive login, which is what makes the browser/login page pop up. A genuinely expired or revoked login reports differently (invalid_grant), so those still correctly need a real re-login.

@Navid200'''s experience is actually the intended behavior — a brief disconnect should just resync on reconnect without prompting. This edge only bites when the token happens to expire during the outage.

Fix in #4608: on a transient network/server error, keep the existing session and retry silently on the next sync instead of forcing a re-login. @michaelcadilhac — if you can run a build with that change, the login page should stop appearing on flaky networks and Tidepool should resync on its own once the connection returns; that would confirm it in the field.

(The SocketTimeoutException upload lines and the Ignoring invalid bg line are unrelated and harmless. The Dexcom G7 reconnect issue is almost certainly a separate, Bluetooth-side thing rather than network-related.)