| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
macOS Tahoe returns a compatibility version, 16, for macOS 26 unless it is built with Xcode 26's SDK. As we did with Big Sur, this maps the compatibility version 16 to 26. The intention is that we will be on the new SDK by the time macOS 27 rolls out. If not, then we will need to add another compatibility map, most likely. It does not appear that iOS, tvOS, or Catalyst return compatibility numbers, so they are excluded from doing any mapping.
|
Tagging subscribers to this area: @dotnet/area-system-runtime |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Backport of #116536 to release/8.0-staging
/cc @akoeplinger @vcsjones
Customer Impact
macOS Tahoe returns a compatibility version, 16, for macOS 26 unless it is built with Xcode 26's SDK.
Since we're relying on Azure Pipelines macOS images and don't control when they bump to the new Xcode SDK we could have a period of time when e.g. Environment.OSVersion returns 16.0. This also impacts checks like OperatingSystem.IsMacOSVersionAtLeast(26).
To address this we remap the version from 16 to 26, just like we did the last time when Apple changed the versioning in macOS Big Sur.
Regression
No, this is caused by changes in Apple's newest OS release.
Testing
Manual testing.
Risk
Low. This just remaps a version number that would be returned on the new macOS release.