question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

xcode-version 12.0 points to Xcode 12.2 beta

See original GitHub issue

I am using the following configuration:

steps:
    - uses: maxim-lobanov/setup-xcode@v1.1
      with:
        xcode-version: 12.0

This leads to the action using Xcode 12.2: Bildschirmfoto 2020-10-04 um 16 27 34

This is wrong as I expect the action using Xcode 12.0 as specified.

Workaround: latest-stable does use Xcode 12.0 as expected

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
maxim-lobanovcommented, Oct 4, 2020

Hello @JonnyBeeGod ! Thank you for reporting!

I was able to reproduce this issue from my side. Based on my investigation, it is an issue with parsing YAML on GitHub Actions side rather than issue with this action. When you pass 12.0 as task input, .0 is trimmed by GH and value is passed just as 12. image image Based on this input, action works as expected. If you pass 12, it selects the latest Xcode 12.x. It is 12.2.0

A few interesting examples below:

  • if you pass version xcode-version: 12 - the value come to task as string 12
  • if you pass version xcode-version: 12.0 - the value come to task as string !!! 12 too.
  • if you pass version xcode-version: 12.0.0 - the value come to task as string 12.0.0 as expected.
  • if you pass version xcode-version: '12.0' - the value come to task as string 12.0 as expected.

I am not familiar with YAML specification to say whether it is a bug or expected behavior. Looks like

  • If quotes are used '12.0' it is clear that it is a string and shouldn’t be cut.
  • If quotes are not used, value is interpreted as a number, so it sounds logical that 12.0 is parsed as 12. 12.0.0 can’t be interpreted as a number, so it is kept as string without cutting.

I see a few options to unblock you:

  1. use xcode-version: '12.0'
  2. use xcode-version: 12.0.0
0reactions
JonnyBeeGodcommented, Oct 6, 2020

sure, all good. Thanks for responding so fast!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Downloads and Resources - Xcode - Apple Developer
Find Xcode downloads, tools, documentation, tutorials, videos, and more. ... Access the beta version of Xcode (when available) to take advantage of new ......
Read more >
Xcode 12 Release Notes | Apple Developer Documentation
The Xcode 12 release supports on-device debugging for iOS 9 and later, tvOS 9 and later, and watchOS 2 and later. Xcode 12...
Read more >
Xcode 12.5 Release Notes | Apple Developer Documentation
The Xcode 12.5 release supports on-device debugging for iOS 9 and later, tvOS 9 and later, and watchOS 2 and later. Xcode 12.5...
Read more >
Xcode - Support - Apple Developer
Xcode Version Minimum OS Required Simulator Swift Xcode 14.1 macOS Monterey 12.5 iOS 12.4‑16.1 tvOS 12.4‑16.1 watchOS 7‑9.1 Swift 4... Xcode 14.0.x macOS Monterey 12.5...
Read more >
Xcode 14 Release Notes | Apple Developer Documentation
Workaround: Build AppIntents code with Xcode 14 beta 6, or on a Mac running macOS Monterey 12 with Xcode 14. Xcode 14 cannot...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found