Ultimately, this issue in iOS 17.5 is Apple’s doing. Hopefully, it gets resolved soon, but when it does, it will merely be a plaster on a bigger issue that the company started way back in ...