-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop silent iOS updates with hard minimum requirements on xcode #19934
Comments
Not sure if this is related, but we are suddenly getting errors on nuget restore because of a changed iOS version:
Builds were doing fine a week ago and no changes have been made to our code. Building against the macOS-13 agent, but the macOS-latest is also not working. What is changing in these agents that builds are suddenly not working anymore? And is there any way for me to fix this? |
So apparantly it is/was in the install maui steps... Previously the following packages where installed: And now suddenly: |
--from-rollback-file https://maui.blob.core.windows.net/metadata/rollbacks/8.0.6.json added to the install maui task solved my issue. But I still don't understand why I suddenly have to... |
FYI, macos-latest is macos-12, not macos-13. Which might make sense why it installed a lower version 17.2 -> 16.4 I don't think this is the same issue as mine as you changed the OS that you're running on which, in turn, has different defaults or maximum versions. My issue is that the underlying iOS nuget package was updated for the same SDK version, and how it has a new minimum requirement. I changed nothing, and with .net8 pinned, it still did an upgrade the broke the build. |
@svaldetero both runs were against the macos-13 agent... It just suddenly stopped installing 17.2 when installing maui. |
I believe this is due to packages being updated during a workload install, so some are not yet published/indexed/available on NuGet.org feed while the command is run. Related: dotnet/sdk#23820 |
@Redth This issue is more that the same SDK version increased the minimum version of something else (xcode). And that new minimum version was no longer the default installation. |
Ahh yeah sorry, I misunderstood this one as it was linked from another related to package publishing. We do have plans to try publishing multi targeted macios workloads and then try to always build MAUI against the older target platform version to avoid this type of issue in the future. |
Hi, @svaldetero |
In these scenarios you probably want to pin a version as much as possible. You should be able to do so with what is described here. Otherwise unfortunately there is not much we can do. This is something that comes from the .NET for iOS layer. Hope this helps! |
Description
I have a maui ios app the builds in Azure Devops Pipelines. It builds fine on monday. On Tuesday it now has a build error. The reason is that Microsoft.NET.Sdk.iOS.Manifest-8.0.100 nuget / workload was updated from 17.0 to 17.2. Which now has a hard requirement on XCode 15.1. I previously pinned the Xcode version to 15.0.1 since that's what was required before and xcode 15 is not the default version on macos-13 image.
This scenario has happened several times before with .net7.
Does every minor update imply a new xcode requirement? I'm even pinning .net to 8.0.x, but that didn't help since it is still 8.0.100 but the workload went from 17.0 -> 17.2.
For reference, here are my steps to setup the build:
I comment out the xcode step when the default is the correct version, however this problem inevitable happens again at some point.
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
8.0.5
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
8.0.3
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
Update my pipeline to select a different xcode version OR update the workload install step to pin to a specific rollback file using an undocumented parameter.
Relevant log output
The text was updated successfully, but these errors were encountered: