-
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
Default Xcode will be changed to Xcode 12.0.1 on October, 20 #1712
Comments
Hi, is it possible that not all machines have Xcode 12 installed yet? Sometimes we got a machine which runs the build job on an Xcode 11.7 and fails of course, although we have specified the path for the Xcode 12. |
@DjCantor , this particular change was not deployed yet at all. |
@maxim-lobanov thanks for the info, I tried to specify the Xcode version in our pipeline in the xcode job, by setting the path to it (as stated in the documentation). However this does not work. What do you mean by share public repro? |
If it fails for you in public repository - give the link to repository. P.S. For GitHub Actions, You can try to use setup-xcode to switch Xcode to check if it works better |
I am using it from Azure Devops. Do you know maybe where can I get support for it? It's not on a public repository. The issue is, that although I specified in our job in the Xcode5@ yaml task to use the Xcode 12 (by specifying the path), but it tries to run on a Xcode 11.7. |
Okay, let's try to localize the problem. If output contains |
Yes, it's an issue with the Azure Devops than, because I see all the newer Xcode versions. Thank you for your help! |
The new image with Xcode 12.0.1 as the default one has been deployed |
This prevents surprising build breaks caused by changing defaults. xcode-select and the setup-xcode-version Action have no effect on OpenJDK's configure. Triggered by GitHub changing the default Xcode to 12 on Oct 20: actions/runner-images#1712
Xcode has been changed to default to Xcode 12.0.1 (actions/runner-images#1712), but this breaks the build. This change pins builds to Xcode 11.7 until it can be fixed.
…t build Xcode for GitHub actions has been changed to default to Xcode 12.0.1 (actions/runner-images#1712), but this breaks the build. This change pins builds to Xcode 11.7 until it can be fixed.
Xcode for GitHub actions has been changed to default to Xcode 12.0.1 (actions/runner-images#1712), but this breaks the build. This change pins builds to Xcode 11.7 until it can be fixed.
On October 20th, 2020, the default Xcode version of GitHub Actions was switched from 11.7 to 12.0.1, breaking the CI. See actions/runner-images#1712 The macOS version is also fixed to avoid similar issues in the future (latest = 10.15 right now)
My MacOS agent (Azure DevOps) still doesn't have Xcode 12 installed.
|
@brian-g Based on the list of Xcode, you use MacOS 10.14. |
Thanks. After much frustration, I realized we were using the legacy Mac OS Agent rather than Azure Pipelines. |
Now that Xcode 12.2 is being added (in #2054), can we discuss a date when it becomes the default version? |
Xcode 12.2 will become default on 30 November: #2056 |
Support for Clang 10 was removed from CI image in actions/runner-images#1712.
Breaking changes
Default Xcode version will be switched from 11.7 to 12.0.1
Target date
Deployment of these changes will be started on 20 October and will take a few days.
The motivation for the changes
We would like to provide the latest stable Xcode by default on images. Also it will mitigate compatibility issue with Xamarin.iOS 14.0.
Possible impact
If you use default Xcode version and your project is not compatible with Xcode 12.0.1, your build can be broken.
Also Xcode 12 has some known issues with Carthage: https://github.com/Carthage/Carthage/blob/master/Documentation/Xcode12Workaround.md
Mitigation ways
Please consider switching Xcode in runtime to version that you need to build app.
The following snippet can be used to switch Xcode:
The text was updated successfully, but these errors were encountered: