-
Notifications
You must be signed in to change notification settings - Fork 24
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
Crossover doesn't read external ssd after patch #146
Comments
Please reference the image found in the following release https://github.com/italomandara/CXPatcher/releases/tag/V0.4.1 |
Similar problem with V0.4.2, when I run with options |
it's a known issue to give the permissions to access the drive try "run command..." and then select any executable of any game in your external drive. |
Is this why it can't find bottles on external volume after patching? Explains my original issue i closed and new issue i was about to open (i tried the new user enterable custom bottle location and that doesn't work either, if bottle is on external volume) When did this break though. like i said patched crossover used to access external volume bottles just fine. on Sonoma. 🤷♂️ EDIT: where folder is, but it doesn't load it at all on launch. |
I've tried granting full disk access. I've tried granting developer mode (god access basically). once crossover is patched it's like it's utterly forbidden from seeing an external disk. I even tried creating a symbolic link pointing to external disk that wasn't on an external disk, and macOS still forbid the patched app from seeing it. |
I'm able to access and use bottles on my external volume, so i can't replicate the issue, have you checked the permissions? What is your volume's file system? |
try this: |
Sorry I didn't get back, I'll try in a few days. gonna be slammed for a few and not have time to play with retesting it |
After that crossover won't launch |
Right it seems like once you disable it it can't be re-enabled |
I think when we remove the code signature, the app loses the entitlements, so you either re-allow the app to access the volumes by running any game in that volume once using run command... or we give the possibility to not disable the signature which is being worked here: https://github.com/italomandara/CXPatcher/pull/147/files |
Toggled the signature option off. still immediately loses access to external volumes and bottles on patching with no way to get it back. 🤷♂️ I don't know what's going on cause I can literally replace every file patcher does manually and this doesn't happen. every lib every config everything manually swapped and it's fine. EDIT, fixed it |
The plist info change is to block auto update so it isn't relevant to the signature. |
My problem is that to run an exe, you need working bottles, all of mine are on external volume, so crossover is just in a unusable state without being able to request new permissions, but undoing plist change on top of signature change being off did let existing permissions seem to keep working, so I have a workable solution now at least :D |
I made that an option will be added in the next release |
Another workaround, try this: In theory you only need to do this once. |
@MysticalOS could to try this Pre-Release to see if it fixes the External HD path issue please? |
If it's regarding ceba6ed it wouldn't work on my system. codesign has been busted for ages and i've no idea why. when it runs it complains no valid codesigning authorities even though I have several valid developer ones. xcode works fine but the codesign sub process is just fubared I'm also using the wine 9.6 based preview fully to help get that early feedback in :D |
correct |
Hello, I just googled the issue and stumbled upon this, I can confirm latest pre-release does allow me to use my external disk again. Thanks a lot. |
Nah, I didn't pop up any windows that asking for permission |
Crossover doesn't read any content in my SSD and can't access my main steamlibrary after patching it. I tried giving both steam and crossover full disk access in the settings but the SSD still wont show its contents.
The text was updated successfully, but these errors were encountered: