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
ensure_xcode_version
uses xcversion
but has not been deprecated
#20866
Comments
It seems like you have not included the output of |
@fastlane-bot I haven't added the |
Update: I was wrong. This is currently possible with However, there might be some additional error handling to implement
|
I started working on this via #20867 |
Hi @mokagio ! 👋 Thanks for bringing this up! There were a total of 4 actions either using
I made a mistaken in not documenting why I didn't deprecate And if you feel like working on its deprecation, that would be super helpful! Feel free to tag me for review if you decide to do it, I'd be happy to help you review it! 😊 |
Thanks for the additional info @rogerluan ! Gotcha. The non-strict version checking is indeed challenging to port over. Not sure if you knew, but |
I didn't know that! But it makes sense now, looking in hindsight, because it uses the Ruby's (I think native?) Gem Version resolution, which accepts that syntax. Since Definitely something we could take a look at. Thanks for bringing this up! |
I started a discussion here XcodesOrg/xcodes#246 |
New Issue Checklist
ensure_xcode_version
dates 2020Issue Description
#20672 deprecates
xcversion
in favor ofxcodes
. However, I noticed that theensure_xcode_version
action has not been deprecated.Suggestion
The most straightforward course of action would be to deprecate it in favor of
xcodes
alone.On the other hand, there's something nice about
ensure_xcode_version
which is that it merely fails the lane if the local Xcode version doesn't match the expected one without attempting an installation or version switch, something currently not possible withxcodes
.A use case for failing over switching is a CI setup where the Xcode version is controlled via a configuration setting that spins up an appropriately provisioned machine or VM and where it's best to update the configuration to match the desired version of Xcode rather than downloading it on every build.
With that in mind, an option going forward could be to update
ensure_xcode_version
to usexcodes
under the hood. It should be possible to parse thexcodes installed
output looking for "Selected" and compare with the given version or.xcode-version
file.It might also be possible to keep the
strict
checking behavior.The text was updated successfully, but these errors were encountered: