macOS - 20250226.755 - Missing iOS Platform #11683
Comments
|
This seems fairly self-explanatory but if you require more logs or information. I can provide them. Thanks. |
|
Hi @jenyangk , We will look into the issue and keep you updated on any further updates. |
|
As a workaround, I install the iOS 18.2 SDK on my pipeline run. Got the hint from this issue - #11335 (comment) This is what I added after I set Xcode version to 16.2:
Sorry about the formatting above. This is what the yaml should look like: 
See an issue reported at dotnet/macios indicating that latest stable release of .NET MAUI (9.0.40) relies of 18.2 currently: dotnet/macios#22243 Just taking the chance to provide constructive feedback. If it is at all possible, we (MAUI developers) need the maintainers of these runner images in sync with the MAUI build requirements. Last issue I had some time ago was with the iOS apple certificate signing. So it is not the first time. Our development for enterprise MAUI apps can be disrupted by pre-releases deployed to our Azure DevOps pipelines. |
|
We are experiencing the same issue, but on the macOS-14 ARM64 (yaml label We're pursuing a workaround similar to what justin-darmody suggested although it will be much easier to have the 18.2 simulators included. |
|
Same issue for us on |
|
I'm facing a similar issue, running on |
|
Adding in the yaml before the build action results in the issue being gone, the output now looks like Maybe there is something off in the preinstalled iOS simulator/runtimes on the macOS 15.3.1 images. |
|
@Arno-Schneider Yes, the same is true for me (with the 15.3.1). The weird part is that there was no announcement about 15.3.1 deployment and the docs says it's still run on 15.2 (https://github.com/actions/runner-images/blob/main/images/macos/macos-15-arm64-Readme.md) Unfortunately, the whole macOS setup has been a mess for the last few weeks. Anyway, I solved this by the Hope they sort it out soon... |
|
@kober32 Yeah, my first approach was to just use |
|
The release notes for 
|
|
There is this: |
|
Getting the same problem on our Azure devops hosted agents. |
|
We are seeing the same issue on Runner Image Version: 20250127.727 does not have this error, our builds succeed. Other versions fail with the above reported error. |
|
@kober32 Can you explain your workaround pls? |
|
Hey @15mgm15, as few have already mentioned here, the workaround is to ensure the iOS platform support is installed on the Microsoft-hosted macOS agents before your build runs. This is similar to the solution from this dotnet/macios FAQ but in CLI. You can add this script to your build step: Setting the XCode version might help. |
|
@jenyangk Got it right then! Thanks for pointing it out. |
|
This is the second time it happens in 2 months. Last time it was #11335 and a few more issues related to it. I understand this is complicated but like @justin-darmody said at the end of his post, this is really disrupting the pre-release process of MAUI Apps. Hopefully I wasn't in a hurry to release a hotfix or something, this could have been bad since there's no ETA on when this is gonna be fixed. I also understand that there's a workaround to install the missing parts, this is cool and useful, but we shouldn't need to put workarounds in our Pipelines or Actions once in a while to fix something that should just work. Just to be clear, I'm not mad, just really annoyed and disappointed. Isn't it any release process to validate that all the parts are there before pushing these image to the world? For information, I'm selecting XCode 16.2 in my Azure DevOps pipeline running on macos-14 image. Worked perfectly yesterday. |
|
This is affecting more than just MAUI apps, as near as I can tell. It appears to also be when running tests on a native app. We have not yet tried the workaround. |
|
We are running into this issue with an Azure hosted agent running |
|
We are getting the same error with Example: https://github.com/JuulLabs/topaz/actions/runs/13597003236/job/38016014230 We will have to try the download workaround but it would be nice if the machines were configured correctly. |
|
If I'm reading the output correctly, it seems like there are no iOS simulators installed: xcodebuild error |
jenyangk
changed the title
|
Hi @jenyangk @JaviSoto / @larry-cariq - Yes, iOS 18.2 is not available , we are currently working on it . We could see iOS 18.3 is available in the images , could you please re-try with that option. 
|
|
Having the same issue. Builds failing. |
|
We experiencing the same issue |
|
Same issue, 18.2 missing. Please fix it soon |
|
This is really frustrating, especially because the workaround of installing the 18.2 simulator manually increases the build time by 10 minutes which in our case is very close to 1 hour timeout bringing our builds to fail anyway. Please fix it asap! |
|
What I don't understand is how a change with a massive regression that broke the product for literally every single developer relying on GitHub Actions for iOS development was deployed without some kind of canary process first, and not only that, but when dozens of developers report the issue (and even escalate it to Microsoft), a day later it's still not resolved. This should've been an immediate rollback of whatever change broke this. It makes me seriously question whether this service can be relied upon for any kind of production use case 😕 this is incredibly disappointing, GitHub. |
|
@prasanjitsahoo @subir0071 @ijunaidm1 Any update on this critical issue? This issue causes long build to fail which causes lots of long reruns which is costing us a lot of extra money. Any progress details you can provide would be helpful. |
|
@susmitamane ^^^ |
|
Heads up! 👋 We are starting rollback for |
|
Hi @erik-bershel, does this mean that the 15.3.1 deployment is postponed until this issue is resolved in the image? |
Thank you Erik. |
It's hard to tell at the moment. We will check why the default runtimes were changed to a set that does not meet the needs of the majority, decide what to do about it and roll out a new image. There is a possibility that we will not fix this issue if the changes were made on the Apple side and were intentional and justified by some unknown circumstances. In any case, the next update will contain OS updates.
Yes, macOS-based Larger runners are based on the same images as Standard runners, so the current rollback will effectivelly affect all of mentioned. |
|
There was a similar defect with a previous macos-image(s). Just as a curiosity, do you have any suite of tests, with different projects and command builds for Xcode with different platform simulators to catch these kind of missing components in the image? We have 18.1, 18.3, but no 18.2.. Isn't it concerning that Github has no reliable release process in place? |
At the moment, Xcode platform tools are an optional component and are not included in the Support Policy to be delivered, since users can install them at runtime, unlike Xcode itself. We are trying to meet the community needs and working on providing them "as much as possible" within a single image (using the command We will consider including those components in the list of service promises, but this will require some changes in the model of platform tools installation and some time in order to provide a certain level of service. |
erik-bershel, |
erik-bershel
added
bug
|
I can confirm situation is back to normal following the rollback on our end. Hopefully this is the last time we hit that roadblock. Twice in two months, one time beginning of January and now 1 time at the end of February and many days to recover is a lot of time wasted. We are lucky to have some understanding clients that trust us but this is not the case for everybody.
I mean that would be great I think, but as we've seen with this situation, installing the simulators adds up a good 10 mins on the pipeline execution time, minutes that we end up paying for at the end of the month. So it's not a win for anybody except the image maintainers that wouldn't need to care about it anymore. ONE other thing that'd be great, I'm using Azure DevOps, it would be absolutely awesome if we could select the actual image with the tag we want to use for our builds. That would just avoid this whole situation since we could just update the image when we really need it instead of always getting the latest version picked up automatically. I know this is a DevOps matter/limitation for all images use on pipelines, not just MacOS, and I should probably post it elsewhere but yeah, that'd be great. Anyway, thanks for quickly rollbacking these changes, really appreciated! |
|
Confirming the issue is fixed, we have removed the explicit simulator download step and everything is building green again, thank you! |
@erik-bershel, according to Xcode 16.2 Release notes it has a new feature:
So |
|
Hey @Vyazovoy!
Yes, we thought about it, but we are not sure that it fits the situation for a number of reasons:
But I would be glad if you share any additional ideas - we will try to work on them as well. |
and others
Description
Hello, I am running into an issue building a .NET MAUI application for iOS with XCode 16.2. It appears that the latest macOS-15 image might be missing the iOS platform as detailed in this known issues FAQ from dotnet/macios.
Here is the error message from Azure Pipelines after using the command
dotnet publish -f:net9.0-ios -c:Release.Platforms affected
Runner images affected
Image version and build link
20250226.755
Is it regression?
20250120.591
Expected behavior
Build should complete without any errors.
Actual behavior
Build fails with this error output:
actool error : No simulator runtime version from [<DVTBuildVersion 21F79>, <DVTBuildVersion 22A3351>, <DVTBuildVersion 22B81>, <DVTBuildVersion 22D8075>] available to use with iphonesimulator SDK version <DVTBuildVersion 22C146> [/Users/runner/work/1/s/Projects/JSI/JSI.csproj::TargetFramework=net9.0-ios]. Indicating missing iOS simulators.Repro steps
Run this command for a .NET MAUI project for iOS on Azure Pipelines -
dotnet publish -f:net9.0-ios -c:Release.The text was updated successfully, but these errors were encountered: