The question I'm asking is "why" - why would Apple ship code that is so horribly broken (from a UI/UX) perspective.
I thought for sure that this slow-temperature-update bug would be fixed in WatchOS 27, but it's just as bad as in 26 and before.
Sometimes the temperature UI will show "--" instead of a temperature, until it finally updates, so clearly they do have code for the "no temperature data" case.
It just boggles the mind that "6 hour stale temperature data" doesn't trigger this same behavior.
The question I'm asking is "why" - why would Apple ship code that is so horribly broken (from a UI/UX) perspective.
I thought for sure that this slow-temperature-update bug would be fixed in WatchOS 27, but it's just as bad as in 26 and before.
Sometimes the temperature UI will show "--" instead of a temperature, until it finally updates, so clearly they do have code for the "no temperature data" case.
It just boggles the mind that "6 hour stale temperature data" doesn't trigger this same behavior.