If a bug has been shipped to production and people are depending on it, it isn't a bug but a feature. If you then "fix" it without notice, it is a breaking change. This is all software/platform development 101.
It isn't. However, there was no release note, it changed late in the beta cycle, and there's no plan to revert.
As of right now, if this isn't adjusted to solve going forward rather than disrupting current applications, I don't have the confidence to upgrade to iOS 18 in a way that I have been confident of earlier releases.
Comments
If a bug has been shipped to production and people are depending on it, it isn't a bug but a feature. If you then "fix" it without notice, it is a breaking change. This is all software/platform development 101.
Just like the coders who rely on electric shocks[0]!
[0] https://programmerhumor.io/programming-memes/stackoverflow-h...
Since when is a beta version of something "production"?
The bug was fixed in the beta. It has been on iOS for many production versions.
It isn't. However, there was no release note, it changed late in the beta cycle, and there's no plan to revert.
As of right now, if this isn't adjusted to solve going forward rather than disrupting current applications, I don't have the confidence to upgrade to iOS 18 in a way that I have been confident of earlier releases.