BG not updating after adding new G6 transmitter or Dexcom Share unless app is force restarted

[LiroyvH]

Describe the bug

Whilst the app is receiving data from the G6 as you can see the latest values in Settings -> CGM (see screenshots), the app won't actually process it until the app is killed and restarted.

Attach a Log

Out of the question in a public database plus its humongous. But will save todays file in case someone wants to analyse it.

To Reproduce

This typically happens when switching transmitters, but I have not seen it getting values but not processing them before. This is the first time I'm switching from ONE+/G7 back to Dexcom G6 (official app since xDrip4iOS is still unusable :() However, for additional context: the app had been without BG data for 7hrs+ due to a ONE+ sensor failure. But all the same: its receiving the values and showing them under CGM, its for some reason just not processing them.

-EDIT- As per the other reports, it turns out the switching from ONE+ to G6 was coincidental and unrelated. (This matches with my previous experiences too, Trio often needs a restart after changing transmitters. Modified report and title as a result)

Expected behavior

Since the app is clearly receiving the values, it should process them.

Screenshots

Setup Information (please complete the following information):

Smartphone:

iPhone 13 Mini, iOS 18 PB5

Pump:

Medtronic 754, EmaLink

CGM:

Dexcom G6, official app.

Trio Version:

dev 7b34986

Technical Details

Already explained

Additional context

Ignore the "signal loss", this appears very often even if its just completed a fresh loop. Will create another report for that if I think of it.

[dsut4392]

Multiple reports of this on FB as well, on adding a new G6 transmitter to Trio no readings are displayed until force closing and restarting the app.

Same also applies when adding Dexcom Share as CGM source, no readings until after force restart.

Test below: Trio main, deleted configured CGM and added Dexcom share. Glucose reading went stale after 11 minutes elapsed from last reading. Force restarted Trio and reading updated almost immediately from Share.
Uploading log 5.txt…

[LiroyvH]

@dsut4392 Thanks for the addition. Matches my prior experience. Modified title and bug description to remove the irrelevant bit.

[github-actions]

hey 👋 - no triage is done for 30 days 🤐 ... anybody? triage is required!

[LiroyvH]

I'm just here so I won't get fined. (Read: so the bug isn't auto-moved to closed)

[github-actions]

hey 👋 - no triage is done for 30 days 🤐 ... anybody? triage is required!