Remove iOS 16+17 and openSUSE Leap 15.5 #9679
Conversation
Falco20019
force-pushed
the
adjust-supported-os
branch
from
f9e4dc6 to
5c2638d
Compare
|
Context: https://endoflife.date/ios |
|
@rolfbjarne and @dalexsoto can comment on the support status of iOS 16 and 17. It seems like we probably support iOS 12.2 and higher, though? |
|
This isn't a question of compiler targeting, but what we commercially support. Apple doesn't support users running iOS 12. This same distinction is clarified in this recent issue: dotnet/runtime#109939 |
I'm not sure this is the best place to check what Apple supports or not (no idea what would be though), because it seems older iOS can get resurrected. Example: iOS 15 lost active support in September 2022, but still got a security update in July 2024, almost two years later. Also removing iOS 17 seems rather harsh, since iOS 18 is only a few months old. I wouldn't be surprised if Apple decides to skip new security updates to iOS 17 in the future. Dropping iOS 16 seems fair though, a year has passed since last time. |
|
I also thought that removing iOS 17 seemed quick. Can app devs still upload apps for iOS 17? |
|
According to the discussion on endoflife-date/endoflife.date#6444 there are known unresolved CVEs for iOS 17 and Apple seems to push people towards 18 instead of fixing it. iPadOS 16 also might be EOL (which I didn't include right now). Apple is never officially setting anything EOL, so checking when something is last updated is usually the only real indicator. The only really EOL devices and not the OS. |
|
I'm not seeing any supporting references on this end of life website, not sure where it gets its source of truth from, and I'd be very hesitant to base our decisions on it for iOS/Android. I don't think either Apple or Google do a great job of articulating which OS versions are actually 'supported'. iOSAs @rolfbjarne mentioned, Apple can still push out service releases for older versions and I'm not sure they actually declare anything officially as to which versions are 'supported'. The only thing I can really find from Apple is: Note: Because of dependency on architecture and system changes to any current version of Apple operating systems (for example, macOS 15, iOS 18, and so on), not all known security issues are addressed in previous versions (for example, macOS 14, iOS 17, and so on).. The reality is there's a not insignificant amount of devices on older iOS versions and our customers expect we reasonably support the majority of the addressable market. AndroidI'm less certain about Google, but there's security patch dates in Android now, and I think vendors generally decide how long they support a given OS / device for, so the decision I believe is less up to Google in this case. For their Pixel devices the support time frame has changed over the years, some had 3 years, it looks like starting with Pixel 8, Google is promising 7 years of security updates - however they don't state which Android OS versions this will apply to. There's also updates to things like AndroidX and Google Play Services which arguably make the concept of a support OS version even more ambiguous. I think the end result here is we need to make some reasonable decisions based on what the runtimes are capable of and what the market share / distribution looks like for the platforms. For .NET 10, I think my recommendation would be:
However, I think there are other stakeholders that should have input to the final decision there too. @steveisok @dalexsoto @jonpryor @davidortinau and any others ya'll would suggest? |
Starting 2025 Apple will limit store apps to target using iOS 18 SDK. Most probably limiting it to Xcode 16. While Xcode 16 still supported deploying for iOS 12, Xcode 16.1 already dropped it and moved up to iOS 13. Our note about min targeting 12.2 then might be increased by that point to 13.x (whatever is still supported by the SDK). |
xcode deployment min targets does not still dictate what addressable OS versions an app can support are, but this is not a data point in making our decisions of what to declare support for. |
|
@Redth iOS 15 was already removed from .NET 8+9 in the past, so 16+ would be the better fit then. Android is currently on 12+ which according to https://apilevels.com/ means 68.7% of all devices (cummulative usage), while 13+ means 55.6%. I would therefore adjust the change to the following instead if that matches your expectations:
I requested the EOL for iOS 17 to be removed again: endoflife-date/endoflife.date#6444 (comment) |
|
Hello, I give some context from endoflife-date/endoflife.date#6444 Apple doesn't publish any information about what versions they support but we can learn from history. The newest version of iOS receives security updates for all devices. The previous version only receives security updates for all devices until December. Beyond December, previous versions only receive security updates for devices that cannot update to the newest version. All devices on iOS 17 are capable of updating to iOS 18, therefore iOS 17 will not receive support. iOS 16 might receive a future surprise update because the iPhone X and 8 are stuck on it. |
Relates to #9638
I removed iOS 16+17 because they ended before .NET 10 was released. iPadOS 16 and 17 is still supported by Apple.
Please check if the versions marked as supported are really already supported. I only updated the JSON now as discussion base based on what the currently available and non-EOL OS are.
/CC @richlander @sbomer @leecow