That is a … WOW. What the F**** is Apple thinking.
View attachment 1995566
Yep, thats all on purpose…
Let me „try“ to simplify Apples anticompetitive dependency hell with fictive versions.
Apple releases iOS10 + XCode 10, and set up a rule that Devs must renew the App certificate with a new App upload from time to time.
Time passes and later they define that new App updates must be done with Xcode 13, and at the same time they remove the iOS10 SDK from Xcode 13.
That means, that all devices which got iOS10 as their last OS update becomes incompatible with the newer enforced App versions. Remember, that devs are not allowed to update an App with an older Xcode than 13 anymore.
Devs are dragged by Apple into a corner where, if they update the App, older users can’t download this App anymore.
So the Dev choose to leave the older legacy App till its certificate expires in AppStore to not instantly upset users of older iDevices, and sometime later this Apple „Dev friendly reminder“ arrives by email into the Devs inbox.
This leads to people buying more iPhones, because their favorite App disappeared or became incompatible with their „old working“ iDevice, a.k.a. planed obsolescence. This also enforces Devs to release „with older devices“ incompatible Apps, and makes sure they can’t continue supporting owners of these still working older iDevices. To achieve their goal even better, they sign iOS updates and stop signing older versions, to stop users from rolling back to older iOS versions.
A anticompetitive dependency hell, and thats only the top of the mountain!