Invalid architecture param is passed to install-scripts for Mac OS (M1) when sdk >= 6.0 is requested

Hi Team,

Recently, an issue landed in the install-scripts repo after fixing the issue for MAC OS (arm64). macOS ARM64 source-build of v6.0.1xx fails The customer uses dotnet-installer and it looks like you have a fallback mechanism that doesn’t work as expected after applying a new rule: When Mac OS runs on arm64:

• if a customer requests sdk < 6.0 , try to install the package for x64 (if Rosetta is detected);
• if a customer requests sdk >= 6.0 then the package for arm64 has to be installed.

In the customer’s ticket, I can see that in “Successful logs” (before the rule implementation), the installer was applying some logic for changing the architecture: Unknown CPU arm64 detected, treating it as x64.

I hope you can find all the required information in the linked ticket. Thank you.

[michellemcdaniel]

So the customer who reported the issue was cloning the repo at a specific release tag, aka one of these: https://github.com/dotnet/installer/tags. We can’t actually update the code associated with a given tag because they are tied to specific commit shas. The fix Epsi made will inly apply to the repo going forward, so the customer will be unable to source build at the 6.0.109 tag that they were using. They will have to either build from the tip of a different 6.0.xxx release branch once it gets these changes, or intentionally replace the dotnet-install.sh script provided by arcade in their local clone.

[michellemcdaniel]

What we are saying is that the copy that is in installer for this branch/tag is out of date. The version in arcade itself is correct. Installer needs to take an update from arcade. Epsi, can you check to see what is on the arcade 6.0 branch, so we can Confirm everything is correct on the arcade side