3 ms·
From what the article says, this is specifically a problem when updating from an OS version released two days ago, to the other OS version released two days ago
by wtallis 1y ago
From what the article says, this is specifically a problem when updating from an OS version released two days ago, to the other OS version released two days ago. That's not exactly the most logical or likely path for most users to take, though obviously Apple needs to be able to handle this going forward for users who are hesitant to update to 26 and want to run 15.7 in the meantime.
- sugarpimpdorsey 1y agoAre you implying none of this code existed more than two days ago?
- wtallis 1y agoOf course not. But it makes sense that a bug with a narrower scope is more likely to escape testing, and apparently something that changed between 15.6.1 (released a month ago) and 15.7 (released two days ago) affects the process of upgrading to 26. So whatever code is at fault is probably pretty recent.