Closed surendrapatel-rak closed 1 week ago
Hey @surendrapatel-rak
It's expected behaviour. Consider to switch to macOS-15 images, please, in order to use Xcode 16.
Thank you, let us know if there are any other issues with we can help.
Hey @surendrapatel-rak
It's expected behaviour. Consider to switch to macOS-15 images, please, in order to use Xcode 16.
* [[macOS] Support policy changes; Xcode 14 and 16 will be removed from macOS 14 on November 4 #10703](https://github.com/actions/runner-images/issues/10703)
Thank you, let us know if there are any other issues with we can help.
Could you, for the sanity of your users, update documentation when you do that!!!!!
https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md
Hi @grafikrobot This week deployment is completed till ring 0 and 1, once all rings completed and changes are deployed it will reflect above changes in the macos-14-Readme.md .
Thank you, please let us know if there are any other issues with we can help.
Checking on that, Thankyou
Hi @susmitamane , Any idea on this error: (This I was getting sometimes in macOS 14 also) Sometimes it works well.
/usr/local/bin/openssl pkcs12 -in /Users/runner/work/_temp/**.p12 -nokeys -passin pass:*** | /usr/local/bin/openssl x509 -sha1 -noout -fingerprint -subject -dates -nameopt utf8,sep_semi_plus_space
Error outputting keys and certificates
401B0F54F87F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:355:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()
Could not find certificate from
Certificate installation is not working even once with macOS 15
@surendrapatel-rak its because you are getting bounced between 2 versions of the macos-15 image. Older version is forcing OpenSSL 3 to be the default and the newer one has that change reverted. My solution has been to just add 2 versions of the install certificate task, 1 with the legacy flag being passed and one without. Add continueOnError: true to both tasks so that your pipeline won't fail when one doesn't work.
Hi @surendrapatel-rak
We have decided to add xcode16 back to macOS-14 images. The deployment is in progress, It may take 3-4 days to complete. Will update here once the deployment is completed.
Thank you.
Hi @surendrapatel-rak
We have decided to add xcode16 back to macOS-14 images. The deployment is in progress, It may take 3-4 days to complete. Will update here once the deployment is completed.
Thank you.
I hope this means there will be better communication with changes like this in the future. This was very close to the release window and definitely not enough time for everyone to get off of macos-14. Xcode 16 was just released.
Thank you for rolling this back, but please, work with folks trapped in this ecosystem before suddenly shifting it around without any public notice. I've said elsewhere, a PR comment is not public notice, it's the information being "publicly available" on a board behind a building with no exterior lights at midnight.
Hey @surendrapatel-rak :wave: We are closing this issue as a partial duplicate and to track the updates on this issue here: https://github.com/actions/runner-images/issues/10703
Also we should notice that the problem with certificates is related to the update to OpenSSL@3 which might be tracked here: https://github.com/actions/runner-images/issues/10817. The next images will contain version OpenSSL@1.1 until the task developers prepare for the changes.
Description
On Image: macOS-14 (Build Agent) Xcode version 16.0 is not found throws error and fails pipeline.
Platforms affected
Runner images affected
Image version and build link
Runner Image Provisioner Current image version: '20241106.300' Agent running as: 'runner'
Is it regression?
NA
Expected behavior
Should be able to find Xcode 16.0 version on On Image: macOS-14 (Build Agent)
Actual behavior
Not able to find Xcode 16.0 version on On Image: macOS-14 (Build Agent)
Repro steps
Run pipleline with On Image: macOS-14 (Build Agent) with Xcode 16 projects