starred/PlayCover

Fork 0

mirror of https://github.com/PlayCover/PlayCover.git synced 2026-04-26 08:15:56 +03:00

[GH-ISSUE #159] Permission Error [Ventura] #64

New issue

Closed

opened 2026-03-03 18:54:12 +03:00 by kerem · 8 comments

kerem commented

2026-03-03 18:54:12 +03:00

Owner

Originally created by @allwh1tesay on GitHub (Aug 14, 2022).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/159

Recently, I updated my Macbook 2020 13inch M1 to Ventura Public Beta, and came along with the error that says: "You don’t have permission to save the file “Frameworks” in the folder “Library”.
Some things I used to solve this problem:

Reinstall Playcover X
Restart Computer X
Go into recovery mode and used repairHomePermissions (Discord Idea) X

Possible ways to solve it but just not ideal:

Reinstall and rollback to Monterey (My files and stuff is running on Ventura so rollback is a problem)
Change my computer (Certainly not possible)

Since playcover runs fine on 99% of Ventura Beta Computers, I suspect to be a bug.

note: the log here

Version 13.0 (Build 22A5321d)
Installing PlayTools
System Integrity Protection status: enabled.

/Library/Developer/CommandLineTools

Originally created by @allwh1tesay on GitHub (Aug 14, 2022). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/159 Recently, I updated my Macbook 2020 13inch M1 to Ventura Public Beta, and came along with the error that says: "You don’t have permission to save the file “Frameworks” in the folder “Library”. Some things I used to solve this problem: 1. Reinstall Playcover X 2. Restart Computer X 3. Go into recovery mode and used `repairHomePermissions` (Discord Idea) X Possible ways to solve it but just not ideal: 1. Reinstall and rollback to Monterey (My files and stuff is running on Ventura so rollback is a problem) 2. Change my computer (Certainly not possible) Since playcover runs fine on 99% of Ventura Beta Computers, I suspect to be a bug. note: the log here ``` Version 13.0 (Build 22A5321d) Installing PlayTools System Integrity Protection status: enabled. /Library/Developer/CommandLineTools ```

kerem

2026-03-03 18:54:12 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 18:54:13 +03:00

Author

Owner

@allwh1tesay commented on GitHub (Aug 14, 2022):

Oh and also I do tried everything under SIP disabled, same issue :(

@allwh1tesay commented on GitHub (Aug 14, 2022): Oh and also I do tried everything under SIP disabled, same issue :(

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@elisezhu123 commented on GitHub (Aug 14, 2022):

you should download the command line tools of your Xcode which can make play cover work but as the Xcode in App Store only support 13.4 version you should go to apple developer .com and download command line tools beta 5 for play cover to work

@elisezhu123 commented on GitHub (Aug 14, 2022): you should download the command line tools of your Xcode which can make play cover work but as the Xcode in App Store only support 13.4 version you should go to apple developer .com and download command line tools beta 5 for play cover to work

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@allwh1tesay commented on GitHub (Aug 15, 2022):

you should download the command line tools of your Xcode which can make play cover work but as the Xcode in App Store only support 13.4 version you should go to apple developer .com and download command line tools beta 5 for play cover to work

nope, that did not help either with both the beta Xcode and the beta Command line tools

@allwh1tesay commented on GitHub (Aug 15, 2022): > you should download the command line tools of your Xcode which can make play cover work but as the Xcode in App Store only support 13.4 version you should go to apple developer .com and download command line tools beta 5 for play cover to work nope, that did not help either with both the beta Xcode and the beta Command line tools

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@ohaiibuzzle commented on GitHub (Aug 15, 2022):

Test if you can write normally to ~/Library/Frameworks (Open Finder, press ⌘ + ⇧ + G, put that in, then try creating a folder there)

@ohaiibuzzle commented on GitHub (Aug 15, 2022): Test if you can write normally to `~/Library/Frameworks` (Open Finder, press ⌘ + ⇧ + G, put that in, then try creating a folder there)

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@allwh1tesay commented on GitHub (Aug 15, 2022):

Test if you can write normally to ~/Library/Frameworks (Open Finder, press ⌘ + ⇧ + G, put that in, then try creating a folder there)

Yes I can do that.

@allwh1tesay commented on GitHub (Aug 15, 2022): > Test if you can write normally to `~/Library/Frameworks` (Open Finder, press ⌘ + ⇧ + G, put that in, then try creating a folder there) Yes I can do that.

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@lixin9311 commented on GitHub (Aug 17, 2022):

It seems like we need to move the PlayTools to another place.

@lixin9311 commented on GitHub (Aug 17, 2022): It seems like we need to move the PlayTools to another place.

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@XuYicong commented on GitHub (Sep 17, 2022):

If your username is different from your home directory name, or you did not accept the license, this will happen. Try changing your username to the same as home directory name, or run sudo xcrun cc in Terminal to be asked to accept the license.

@XuYicong commented on GitHub (Sep 17, 2022): If your username is different from your home directory name, or you did not accept the license, this will happen. Try changing your username to the same as home directory name, or run `sudo xcrun cc` in Terminal to be asked to accept the license.

kerem commented

2026-03-03 18:54:14 +03:00

Author

Owner

@IsaacMarovitz commented on GitHub (Sep 24, 2022):

This is resolved in nightlies

@IsaacMarovitz commented on GitHub (Sep 24, 2022): This is resolved in nightlies