Skip to content
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

On Image: macOS-14, Xcode 16.0 is not found #10929

Open
2 of 15 tasks
surendrapatel-rak opened this issue Nov 8, 2024 · 9 comments
Open
2 of 15 tasks

On Image: macOS-14, Xcode 16.0 is not found #10929

surendrapatel-rak opened this issue Nov 8, 2024 · 9 comments

Comments

@surendrapatel-rak
Copy link

Description

On Image: macOS-14 (Build Agent)
Xcode version 16.0 is not found throws error and fails pipeline.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Runner Image Provisioner
Current image version: '20241106.300'
Agent running as: 'runner'
Screenshot 2024-11-08 at 11 32 33 AM

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

Screenshot 2024-11-08 at 11 14 38 AM Screenshot 2024-11-08 at 11 14 19 AM
@susmitamane
Copy link
Contributor

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.

@grafikrobot
Copy link

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

@susmitamane
Copy link
Contributor

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.

@surendrapatel-rak
Copy link
Author

Checking on that, Thankyou

@surendrapatel-rak
Copy link
Author

surendrapatel-rak commented Nov 12, 2024

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
##[warning]Error parsing certificate. This might be caused by an unsupported algorithm. If you're using old certificate with a new OpenSSL version try to set -legacy flag in opensslPkcsArgs input.
##[error]Error: /usr/local/bin/openssl failed with return code: 1

@surendrapatel-rak
Copy link
Author

Certificate installation is not working even once with macOS 15

@zypherman
Copy link

@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.

@susmitamane
Copy link
Contributor

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.

@tsal
Copy link

tsal commented Nov 14, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants