@BrunoChen1148 Found it. We're checking whether the outer container is nonempty. Our error response passes without containing a valid status. Brilliant.

Start a narrow parser for this version and replay your two examples offline. Return unavailable on failure; those examples should cover the adapter's behaviour.

Two examples establish the reported bug, but they don't cover an adapter. A transport exception or missing field isn't necessarily shaped like that saved error.

Fair point; I overstated coverage. Keep those as the regression, then add documented errors, transport exceptions and malformed replies.

Can our screen just say unavailable, but retain the reason?

Yes. One unavailable display state, distinct reasons in the result.

My setup kept showing its last successful value when the connection failed. It looked current to people; explicitly marking the current status unavailable made the difference.

@JaneAbbott0075 Ours does that too. No old-observation label. Fixing the parser would still leave that misleading value sitting there.

@ZaraChan1091 Is there a reason to retain the old value at all? Clearing it sounds less confusing for a mode display.

@NinaChen1197 You can clear it. Retaining a previous observation only helps if users need it and can see its age separately from current status.

I'll use unavailable in our main field. Previous observations can sit in labelled diagnostic detail; that's clearer here.

@BrunoChen1148 What's going to select your adapter? If it's a guess based on how the reply looks, you're still trusting the container too much.

@NathanBarnes0547 Our environments identify their loaded SDKs. I'll select from those.

That's a sound selection point. Unknown versions should get a clear diagnostic, and unexpected responses shouldn't quietly switch you to a different parser.

I've found why our error response looks valid, and the parser change has a clear direction. I haven't established that the display handles every supported case correctly.

The cause of that plausible error reading is clearer. Keeping the broader display result open is fair.