Meaning, effectively, that it will not be fixed.
I understand the frustration. I work on a mobile application that, like Uber, relies on a lot of server-side communication and deliberately stops working if the client is out of date. And I do know that this sucks.
But the reality is, our API is non-public, and so there is no pressure from anyone to maintain backward compatibility. And I have a thousand features that need to ship, with not enough time as it is, or I will start getting heat from management. Abandoning the cadence of "constant breaking changes bundled with client updates" would slow development considerably, for no gain except the one-hundredth-of-one-percent of HN weirdos who care about this stuff. It's just not going to happen.