mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 08:15:56 +03:00
[GH-ISSUE #702] [Bug]: Command line tools installation failed but mac detects the command line tools. #338
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#338
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ThisIsHimaksh on GitHub (Jan 15, 2023).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/702
Describe the bug
I tried installing playcover but it said installation failed. But on opening terminal and writing xcode-select --install tells me that the command line tools are already installed.
Steps to reproduce
Expected behaviour
Command line tools should not be there if installation was failed. Also installation should be succesful.
Crash log
No response
What version of PlayCover are you using?
Playcover 2.0.2
What version of macOS are you using?
Ventura (macOS 13)
Issue Language
@tiagoaosilveira commented on GitHub (Jan 15, 2023):
same here, PlayCover doesn't detect my xcode-select at all even though it's there. Tried removing and reinstalling both PlayCover and XCode terminal tools but it just doesn't work
@ohaiibuzzle commented on GitHub (Jan 15, 2023):
Can you check the output of
$(xcode-select -p)/usr/bin/notarytoolin the Terminal?@tiagoaosilveira commented on GitHub (Jan 15, 2023):
@ohaiibuzzle
@tiagoaosilveira commented on GitHub (Jan 15, 2023):
oh wow, this is embarrassing but I've managed to fix this...
xcode-select command not found errorzshbefore issuing the codezshcommand, it gave me multiple errors of not finding stuff (locale, direnv, etc)~/.zshenvdid the trick for me :)@zanderp25 commented on GitHub (Jan 16, 2023):
Weird. I don't think it should be depending on that.