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.
Sounds like the issue is they corrected the bug without documenting the breaking change and did it with minimal notice. Worse yet is that the API change will impact all software running on the host. So even if your distributed program works today, it will subtlety break when the user upgrades their host OS.
IOS 18 is at RC now and is scheduled to be released on Monday. Existing apps affected by this behavior change will break or misbehave when users update their devices to iOS 18 next week.
