-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[macOS] Support policy changes; Xcode 14 and 16 will be removed from macOS 14 on November 4 #10703
Comments
This is a bit messed up since |
- Days of `macos-12` are numbered: actions/runner-images#10721 Drop 5 affected jobs, replaced by `macos-15` ones added earlier today. - Drop Xcode 14 and 16 from `macos-14` jobs. Following up upstream announcement: actions/runner-images#10703 (No active jobs are affected by this.) Follow-up to 4b4ff44 #15108 Closes #15113
Can we get a response on this? |
Hey @Cheesebaron and @LotskiAndrej! We are working on adding macOS-15 to ADO, but no ETA or promises are available now. I'll publish info in #10686 once available. |
Is there any way to use Xcode 16 currently using macOS-14 ? I run task for checking Xcode version on ADO and got this, but it says it cannot locate xcode 16 |
Yes, we have not removed
Recommended task: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/xcode?view=azure-devops |
Thanks for the response, but since I'm using MAUI, I cannot add xcWorkspacePath, and ADO crashes if I don't enter anything.
But it cannot locate the file |
@mjosipovic-tgr, I am currently using the same command line command you are using with macOS-14 to set it to use Xcode 16 and it works fine.
I'm using the classic pipeline editor: |
I tried it few times, changed the order of the tasks in yaml, and managed to get it to work, tnx for the responses. |
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
Xcode 16 will be removed from macos-14 to cut down on the image size: actions/runner-images#10703
## 📜 Description An attempt to fix iOS 18 e2e tests. ## 💡 Motivation and Context First of all I ahd to run e2e tests on `macos-15` runner because of a recent changes introduced in actions/runner-images#10703 I did it, but then turned out, that `macos-15` doesn't have iPhone 14 by default. I re-generated assets for iPhone 16 Pro, now e2e tests can start successfully, but for some reasons they don't want to pass - many of tests that rely on matching screenshots detects a difference. Unfortunately I can not detect the diff, because we exceed 90 minutes. Taking all information above I decided, that current changes are good enough to be merged - later on I can restore iOS 18 e2e tests in CI, but tight now I want to unblock the process of merging other important PRs. Also iOS 18 tests were not very stable. When I added them I used older macos and older iOS to generate screenshots. Now I updated to necessary XCode version, so I should be able to have 1:1 environment, let's see! <!-- Why is this change required? What problem does it solve? --> <!-- If it fixes an open issue, please link to the issue here. --> ## 📢 Changelog <!-- High level overview of important changes --> <!-- For example: fixed status bar manipulation; added new types declarations; --> <!-- If your changes don't affect one of platform/language below - then remove this platform/language --> ### E2E - changed iPhone 14 to iPhone 16 Pro (to match previous versions); - regenerated assets; - lock simulator18 version; ### CI - run iOS 18 tests on macos-15; - exclude iOS 18 testing from CI; ## 🤔 How Has This Been Tested? Tested on CI. ## 📝 Checklist - [x] CI successfully passed - [x] I added new mocks and corresponding unit-tests if library API was changed
We need Xcode 16 and that version is now only available on macOS 15 action runners: actions/runner-images#10703
Hey there! 👋 Due to a combination of factors (including some unexpected issues with dependencies on |
Please keep Xcode 16. Thanks to Xamarin.UITest we need to build IPA's with Xcode 16 and run the tests with Xcode 15.4 |
…116216) After a recent Github Actions runner policy change [1], the version of Xcode included in the macos-14 image went from Xcode 16 to Xcode 15, breaking our build bots. This moves the bots to the macos 15 (public preview) image, which contains Xcode 16. Also, adjust an UNSUPPORTED annotation that was incorrectly targeting macos 13.7 when it should have been targeting a version of AppleClang. [1]: actions/runner-images#10703
This is necessary due to this breaking change in Azure Pipelines/GitHub's hosted agents: actions/runner-images#10703
When we will be able to see the changes, Xcode 16 is still not available with macos-14-xlarge runner? |
@erik-bershel I hope you don't remove it from macOS-15 since I managed to got it to work. |
Which Xcode version it works for you in macOS-15? |
@yasali xcode 16 |
@erik-bershel Will this happen on Azure DevOps as well? We have there the same issues like on GitHub Runners, but still don't have the Xcode 16 on mac os 14 again. Our builds are blocked right now. |
This change means it is not impossible to build against iOS 17 and iOS 18. Can the iOS 17 Simulator be added to the macOS-15 image please? |
@yasali , what fix you have given to make xcode16 work on macOS-15. Can you please help me. |
|
Hey there again! 👋
At the same time with the Standard Runners and Microsoft Hosted Runners. We are working on providing ETA and details.
Yeah, it will be there too. The deployment of changes has not yet begun due to preparatory work. But we understand how pressing this issue is and we are really making every effort to speed up the solution to the problem.
It seems we forced to keep it, yes. We will work on another strategy to reduce disk space usage after mitigating the current situation with the |
I will be very grateful if you share the problems you have when migrating from |
@erik-bershel if space is an issue, might I suggest keeping only the latest Xcode 14, latest Xcode 15, and Xcodes 16.x. It's no accident, for example, that when I create a new Xcode app and target a lower iOS version (e.g. iOS 16), by default Apple targets 16.6, not 16.0. This gives us the most stable of each previous version, and a fallback when current versions introduce a bug. Hope this helps |
Hi @erik-bershel , I am running the pipeline in Azure DevOps, using xcode16.1 with macOS-15, getting below error at install apple certificate task. Error message can you please help me on this |
@yeftha For this you can check th solution provided by mjosipovic-tgr in |
Heads up! ⏰ To provide immediate mitigation, we have decided to roll back the current |
Looks like actions/runner-images#10703 took away support for xcode 14. That is why the latest action failed. There an active PR adding support for xcode 16 to the macos runner (actions/runner-images#10967). This commit will fail until that has been merged, but it is probably worth waiting for.
Looks like actions/runner-images#10703 took away support for xcode 14. That is why the latest action failed. There an active PR adding support for xcode 16 to the macos runner (actions/runner-images#10967). This commit will fail until that has been merged, but it is probably worth waiting for.
@MerSpyro This fix is working fine . Thank you |
Breaking changes
Current support policy:
New support policy:
Xcode 14
andXcode 16
will be removed from themacOS-14
image.macOS-12
andmacOS-13
images. The changes will affectmacOS-14
and all subsequent images. As a result,macOS-14
-based images will contain onlyXcode 15.x
versions,macOS-15
images will contain onlyXcode 16.x
versions, and so on.Xcode
beta
is released and there is no next revision of themacOS
image? Such abeta
will be shipped as part of the latestmacOS
image that supports thisXcode
, until the next basemacOS
image is released, for example:Xcode 16
was shipped as part ofmacOS-14
until we releasedmacOS-15
.Target date
November 4, 2024
The motivation for the changes
Recently, mainly due to the introduction of the new
visionOS
platform,macOS
-based images have grown to such sizes that they are becoming more difficult to maintain, and users are experiencing difficulties with available disk space, which is critical for completing builds. Parent issue:Possible impact
Workflows based on
macOS-14
will stop running if they depend onXcode 14
and/orXcode 16
Platforms affected
Runner images affected
Mitigation ways
Users whose workflows depend on
Xcode 14
and/orXcode 16
will be forced to use themacOS-13
image forXcode-14
and themacOS-15
image forXcode-16
, respectively. Be aware thatmacos-13
YAML label refer to Intel-based image.The text was updated successfully, but these errors were encountered: