Open al-cheb opened 3 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
I guess it comes from https://github.com/dotnet/runtime/blob/208e377a5329ad6eb1db5e5fb9d4590fa50beadd/src/libraries/Common/src/Interop/OSX/Interop.libobjc.cs#L54-L61.
Does this mean the .NET Runtime is not yet built "with updated SDK"?
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Tagging subscribers to this area: @dotnet/area-system-runtime See info in area-owners.md if you want to be subscribed.
Author: | al-cheb |
---|---|
Assignees: | - |
Labels: | `area-System.Runtime`, `untriaged` |
Milestone: | 6.0.0 |
I can't reproduce this in .NET 6, I think this is something that only applies to .NET 5 and 3.1.
Both the API and and dotnet --info
are seem correct for 6.0 on my M1 Mac.
This is interesting - it seems that macOS freezes the version you get depending on what SDK you build it with. Based on the code above, it seems that it's getting 10.16 from the OS. It isn't "updating its lie" as 10.17 or similar.
If I tell macOS to not lie about the version, PowerShell starts working accordingly.
If what I said about the version being fixed based on the SDK, then #41012 may need to be revisited.
I guess it comes from
. Does this mean the .NET Runtime is not yet built "with updated SDK"?
Can’t .NET simply set SYSTEM_VERSION_COMPAT = 0
and get rid of the above code altogether?
Since this is global the real question is what else is impacted. I'll check if we can get the real version via sysctl
. Also I'm not sure what is oldest version we need to support @danmoseley. Perhaps it is also time to update the SDK we use.
I got VM up and @vcsjones was right. 6.0 works as expeced and return 12.0 as it it should. This is probably because we use updated SDK and OS does not lie to us. So we should service 5.0 (and perhaps 3.1) @danmoseley but this should not impact 6.0 as far as I can tell.
Minimum supported versions are documented here
https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md
6.0 : 10.14 3.1 and 5.0 : 10.13
Highest supported macOS versions are not documented there but historically I believe we have aimed for .NET versions still in support to support the latest released macOS as generally folks upgrade macOS eagerly. @leecow is that right?
Moved to 7.0.0 milestone to reflect that this does not affect 6.0. Even though it also won't affect 7.0.0, we'll want to service 5.0 and possibly 3.1 for this if there's enough justification, so this will be on the radar during the 7.0.0 milestone.
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
This process is part of our issue cleanup automation.
[Environment]::OSVersion.Version.ToString() should return 12.0.0.
Current behavior:
Expected value: