Build agent still has Xcode 12.5 installed

Archive Tooling Issues
,
1

We’re having an issue where some of our builds (all expecting Xcode 12.5.1) are incorrectly finding Xcode 12.5 on the build agent. These are on the same build plan and were kicked off within seconds of each other

Failing build (https://app.bitrise.io/build/45443ba8-1eb6-47b4-9c7f-8cce0b6481a8#?tab=log):

[22:08:17]: --- Step: ensure_xcode_version ---
[22:08:17]: ----------------------------------
[22:08:17]: $ xcversion selected
[22:08:20]: ▸ Xcode 12.5
[22:08:20]: ▸ Build version 12E262
[22:08:20]: Selected Xcode version is not correct: 12.5. You expected 12.5.1.
[22:08:20]: To correct this, use: `xcode_select(version: 12.5.1)`.
+------------------+---------------------------------------+
|                       Lane Context                       |
+------------------+---------------------------------------+
| DEFAULT_PLATFORM | ios                                   |
| PLATFORM_NAME    | ios                                   |
| LANE_NAME        | ios download_development_certificates |
+------------------+---------------------------------------+
[22:08:20]: Selected Xcode version doesn't match your requirement.
Expected: Xcode 12.5.1
Actual: Xcode 12.5

Successful build (https://app.bitrise.io/build/46a7f222-e325-4351-b7ea-4def3365a02f#?tab=log)

[22:08:26]: ----------------------------------
[22:08:26]: --- Step: ensure_xcode_version ---
[22:08:26]: ----------------------------------
[22:08:26]: $ xcversion selected
[22:08:28]: ▸ Xcode 12.5.1
[22:08:28]: ▸ Build version 12E507
[22:08:28]: Selected Xcode version is correct: 12.5.1
1 Like
2

Hello @elsaberos :wave:

We have recently updated our images, which should mean the issue should no longer come up :slight_smile:
Let me know if you still experience any issues!

3

Hi, I’m still getting Xcode 12.5 installed in bitrise. Is there any update on this issue?
Here is the failing build (Bitrise - Mobile Continuous Integration and Delivery - iOS & Android Build Automation)

| output_xctestrun                               | false                                               |
| result_bundle                                  | false                                               |
| use_clang_report_name                          | false                                               |
| disable_concurrent_testing                     | false                                               |
| skip_build                                     | false                                               |
| slack_use_webhook_configured_username_and_icon | false                                               |
| slack_username                                 | fastlane                                            |
| slack_icon_url                                 | https://fastlane.tools/assets/img/fastlane_icon.png |
| slack_only_on_failure                          | false                                               |
| xcodebuild_command                             | env NSUnbufferedIO=YES xcodebuild                   |
| skip_package_dependencies_resolution           | false                                               |
| disable_package_automatic_updates              | false                                               |
| use_system_scm                                 | false                                               |
| number_of_retries                              | 0                                                   |
| fail_build                                     | true                                                |
| xcode_path                                     | /Applications/Xcode-12.5.app                        |
+------------------------------------------------+-----------------------------------------------------+
4

Hello,

Apologies for the confusion and inconvenience. There were some issues in updating the Xcode 12.5.x stack from Xcode 12.5 to Xcode 12.5.1. These should now be corrected and the xcode 12.5.x stack should have Xcode 12.5.1 now.

If you do have an issue with this, please let us know. The best thing to do would be to open a ticket.

Thanks,
Cathy

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.