xcode-install
xcode-install copied to clipboard
When specifying "13.0", Xcode Beta is installed instead of latest Xcode 13
I observed this when using .xcode-version
with 13.0
instead of 13
. For some reason it installs the Xcode 13 Beta from June (which's probably the Beta 1), instead of the latest Xcode 13 (public release). By changing the version to 13
, it installs the correct version of Xcode.
I know that the Xcode 13 identifier is actually "13" and there's no "13.0" identifier, but this is very counter intuitive 😬
It looks like this tool got stalled in release version 12.5.1 for some reason. Running xcversion update
won't retrieve any of the already released 13.x.x versions.
This tool last commit happened in early September. I wonder if something changed in the app store metadata afterwards. Maybe this tool misses to catch some metadata change and doesn't "realize" that there are new releases available.
It looks like this tool got stalled in release version 12.5.1 for some reason. Running
xcversion update
won't retrieve any of the already released 13.x.x versions. This tool last commit happened in early September. I wonder if something changed in the app store metadata afterwards. Maybe this tool misses to catch some metadata change and doesn't "realize" that there are new releases available.
Maybe my bad: it seems like versions 13.x.x are only available on macOS Monterey. What macOS version are you running, @rogerluan ?
@diegum I don't think that XCode 13 is available only on macOS Monterey, been able to install it on Big Sur
Yeah it's not, Xcode 13 min req is Big Sur: https://developer.apple.com/support/xcode/ To answer your question, though: not sure if I installed while on Big Sur or Monterey. Right now I'm on Monterey, I remember I updated both of them in the same week but don't remember which one I installed first 😂
Experiencing this issue with Xcode 13.3 vs Xcode 13.3 beta 2 - the gem defaults to beta 2.
Interesting @gbrhaz, that's not what I'm observing. I installed Xcode 13.3 and got the right version. Which concludes that this issue is not the same for everyone, so it might not be 100% reproducible - there's something on the way that is causing a non-stable versions lookup 🤔