Closed jazaval closed 4 years ago
@joshdholtz do you mind taking a look at this? Looks like anyone who has an Xcode app bundle previously installed or moved/managed after running xcversion install
is blocked from using the xcversion
CLI.
Yeah yeah! Just out picking up some Thai for dinner and then I’ll check it out when I get home.
Thanks a bunch - really appreciate it. Can’t wait for Xcode 12 next week 🤪
Hi @joshdholtz :) Can we please release it?
@joshdholtz do you need me to bump it to 2.6.6?
Ah sorry! Releasing now 😱 I got so sidetracked but the API fixes 😔 I can bump! Will be released in about 10 minutes.
Should be up on rubygems for ya’ll!
https://github.com/xcpretty/xcode-install/releases/tag/v2.6.6
Thanks!
This PR:
Updates the
appname_version
method to catch cases in which the Xcode bundle has been renamed, in order to resolve #396.Due to the updates in #386,
xcversion
commands will fail with the following error if the user renames the Xcode application bundle to remove the version number from the path, or if they've installed Xcode from another source, like the App Store.Example repro/stacktrace:
This change can impact proper detection of beta Xcode installations in the
xcversion installed
list, but only if the user has performed a Xcode bundle path rename. Given that theCFBundleShortVersionString
fromContents/version.plist
of beta Xcodes does not identify beta seeds directly, this is the only compromise I could think of that would allow for users to rename the Xcode application bundles installed byxcode-install
.