We have released an Xcode 11 GM Seed 1 image today. You can select the image by adding the following to a job in config.yml :
macos:
xcode: 11.0.0
There are some changes from the Xcode 11 Beta 7 image:
Xcode is now version 11.0 GM Seed Version 11A419c
We have added more SDKs and simulators to the image. In addition to the suite of iOS 13 simulators, we have also installed simulators and SDKs for
iOS 12.2
iOS 11.4
tvOS 12.2
watchOS 5.2
To account for the extra disk space for the SDKs, we have increased the diskl size from 64G to 73G, and the free space for running jobs is now 29G.
Minor changes:
Node upgraded from 12.9.1 -> 2.10.0
Fastlane 2.129.0 => 2.130.0
The full manifest of the installed software and SDKs is available here.
Known issues
There is an issue where a dialog appears for the first 30 seconds after the image boots reporting that the OS did not shut down cleanly on the last boot. This might impact UI tests. We pre-boot VMs so that builds can start as quickly as possible, so in many cases our VMs have been booted more than 30 seconds prior before to build running, which will reduce the rate of occurrence of this bug.
Upcoming deprecations / changes
Removed support for Xcode 10.2.0 on Monday, August 26th, 2019. This version has bugs that we fixed in the Xcode 10.2.1 image. At some point soon, all jobs using Xcode 10.2.0 will automatically use Xcode 10.2.1. There might be differences in the dependency versions between the Xcode 10.2.0 image and the Xcode 10.2.1 image. Please upgrade to Xcode 10.2.1 or newer.
Python 2 will be no longer be maintained from January 2020. We plan on removing Python 2 from any images built after that date (Python 2 is being removed from homebrew).
Any idea why xcodebuild fails to resolve package dependencies in this image? I expect this might be an Xcode bug.
I keep getting: Authentication failed because the credentials were rejected, but I canāt seem to debug whatās going wrong. If I ssh into the machine I can clone the offending GitHub repos through ssh, but xcodebuild still fails.
Iāve had the same issue with Xcode failing to resolve package dependencies. I believe itās ultimately caused by this setting in ~/.gitconfig causing all GitHub URLs to be rewritten as SSH URLs:
This isnāt necessary for cloning public GitHub repos, so on my project I added an early build step to my job that overrides this with a much more specific pattern that only matches private repos in my GitHub organisation. This way all my package dependencies are still cloned over HTTPS and donāt hit the SSH host verification issue noted in the Xcode 11 release notes:
When using xcodebuild , resolving packages may fail to verify SSH fingerprints unless that fingerprint is already in the ~/.ssh/known_hosts file. (50686014)
Workaround: SSH into the host and verify the fingerprint from the command line before using xcodebuild , or manually add the host fingerprint to the ~/.ssh/known_hosts file.
Thanks for the quick turnaround. This is so helpful. One thing that would have helped going forward would be to be able to specify which beta we built with rather than being force upgraded. Having your VM change out from under us without changing our config file sometimes caused us to scramble - especially on the betas. Even if you remove the old betas a week later, it would still have given us time to migrate and fix any issues on a newer beta
Yeah, that seems to be a workaround for the problem. Iāve managed to get the public repos working, but the private ones still donāt work (Iāve tried https with url username / password and it rejects the SSL certificate).
I wonder why Xcode doesnāt honor the SSH configuration to allow all keys from github.com, though.
We have the system Ruby installed, as well as the stable releases as documented on https://www.ruby-lang.org/en/downloads/ at the time that we build the image, which is 2.5 and 2.6. Ruby 2.4 is marked as āIn security maintenance phase (will EOL soon!)ā, so we donāt install it.
When installing software, there is a balance that we need to maintain ā the most software that we install, the larger the image, which means that it takes us longer to distribute the images, and we would have to limit the number of images that are available.
Can you email a specific list of the devices and SDKs that you would like to support@circleci.com please? Iāve tried to add iOS 11, 12 and 13 for all devices, so any omissions are probably an error on our part.
Just a heads-up, it looks like Apple have released GM 2 and are now rejecting uploads from GM 1:
[11:50:30]: ERROR ITMS-90534: āInvalid Toolchain. Your app was built with an unsupported version of Xcode or SDK. If you plan to submit this build to the App Store, make sure you are using the GM version of Xcode 9 and the SDK for iOS 11, tvOS 11, watchOS 4, or macOS 10.13 or later. If you are using an Xcode beta version to test your app, make sure you are using the latest supported version. For more information about supported beta versions, view the TestFlight Release Notes (https://developer.apple.com/testflight/release-notes/).ā
iPhone XR (13.0) seems to be missing now (but was present in last beta).
We will need iOS 13 simulators for a lot more devices (all iPhones from 6s onward, inclusive). Reason being: we to run tests on the older devices also.
Any pointers on how to do this?
New to circleci / fastlane and not sure how Iād do this.
If I add a - run step before the - checkout step in the config.yml file:
but thatās not showing this setting so this makes it seem like if I try to change it in this step before checkout itās just going to get overridden by something in the checkout step (?).