Homebrew
Doctor: "Warning: No Cask quarantine support available: unknown reason" #5482
Replies: 18 comments 41 replies
-
|
Your |
Beta Was this translation helpful? Give feedback.
-
I got the same issue when I upgraded to macOS 15.0, The output of the above command is: my brew config: |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue. Thankfully, I run this <unknown>:0: error: PCH was compiled with module cache path '/var/folders/14/07yvz9pj24s2r70gt87n3k2r0000gn/C/org.llvm.clang.zorn/ModuleCache/2ZDVRZCAEUI7H', but the path is currently '/var/folders/14/07yvz9pj24s2r70gt87n3k2r0000gn/C/org.llvm.clang.Zorn/ModuleCache/2ZDVRZCAEUI7H'
<unknown>:0: error: missing required module 'SwiftShims'Then I just delete the cache folder |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if it is relevant, and I'm not totally sure how to test it really, but I also see this error message:
My only suspicion is that I am running the latest MacOS on a legacy Mac, via OpenCore which I think has implications on the strictness of SIP. Maybe that is part of the reason? |
Beta Was this translation helpful? Give feedback.
-
|
Our situation is similar. I am using the hackintosh drived by opencore and opencore-patcher. You can try the command |
Beta Was this translation helpful? Give feedback.
-
|
Oh wild, that one for me gives me And that appears to be a private API internal to Homebrew? It says I am up to date though 🥴 Attempted to reinstall Homebrew with the package and didn't seem to take much effect 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
same error with me |
Beta Was this translation helpful? Give feedback.
-
|
Swift (including the |
Beta Was this translation helpful? Give feedback.
-
|
I attempted a full reinstall of Xcode, that otherwise seems to be running fine and my |
Beta Was this translation helpful? Give feedback.
-
|
Same issue on a brand new re-install of macOS 14.7 M3 Brew doctor:Brew config: |
Beta Was this translation helpful? Give feedback.
-
|
The common factor here in the reports from the last few days appears to be people have CLT 15.3 installed but have the macOS 15 SDK. This should be impossible as only CLT 16.0 contains the macOS 15 SDK. It sounds like something (potentially a bug in |
Beta Was this translation helpful? Give feedback.
-
|
Same issue on macOS 14.6. I only have command line tools installed - not Xcode.
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue after updating macOS to Sonoma 14.7, only I do have Xcode (version 16) installed.
|
Beta Was this translation helpful? Give feedback.
-
|
some problem on sequoia with opencore but all its ok on brew... why this message? |
Beta Was this translation helpful? Give feedback.
-
|
Because some features will not work. |
Beta Was this translation helpful? Give feedback.
-
|
Did some testing on my end and it seems that something probably changed in Sequoia with the Driver file (everything save the first import Foundation
struct SwiftErr: TextOutputStream {
public static var stream = SwiftErr()
mutating func write(_ string: String) {
fputs(string, stderr)
}
}
print(CommandLine.arguments)
var dataLocationURL = URL(fileURLWithPath: CommandLine.arguments[1])
do {
let isDataLocationURLReachable = try dataLocationURL.checkResourceIsReachable()
} catch {
print(error.localizedDescription, to: &SwiftErr.stream)
exit(1)
}
Seems to me that changing I have a normal Monterey installation that I can try stuff on if necessary. |
Beta Was this translation helpful? Give feedback.
-
|
Intriguing... Just checked that the latest CLT from Monterey works as intended with both the driver file (reads one argument and exits because
But the stack dump reports the full call list like Sequoia does...
Just in case, MacBook Pro 12,1, Sequoia is with OCLP, Monterey is natively booted. |
Beta Was this translation helpful? Give feedback.
-
|
It seems that this one liner is enough to demonstrate the problem. Curiously it behaves normally if invoked over print(CommandLine.arguments) |
Beta Was this translation helpful? Give feedback.
-
|
Have you tested it again with Swift 6.0.2 released today in CLT 16.1? |
Beta Was this translation helpful? Give feedback.
-
|
Yes.
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue I re-run it a second time and it succeeds. No idea how to fix yet, maybe homebrew will find a fix eventually. |
Beta Was this translation helpful? Give feedback.
-
|
After a clean install of macOS 14.17.1 (Sonoma) and the latest CLT, I am still seeing the warning as well. |
Beta Was this translation helpful? Give feedback.
-
|
Do you use opencore patcher? |
Beta Was this translation helpful? Give feedback.
-
|
No, just a straight re-install directly from Disk Utilities |
Beta Was this translation helpful? Give feedback.
-
|
Same problem for me, brand new sequoia 15.1 reinstall on an elegible intel macbook air.
After switching xcode-select to Xcode 16.1.0 (installed via xcodes), both the warning and the subsequent swift check error are solved. |
Beta Was this translation helpful? Give feedback.
-
I download lastest command line tools, doesn't work, I try xcode later. |
Beta Was this translation helpful? Give feedback.
-
i install xcode 16.1.0 with app store, it doesn't work, |
Beta Was this translation helpful? Give feedback.
-
|
What do you get when you run: |
Beta Was this translation helpful? Give feedback.
-
OS 15.1 |
Beta Was this translation helpful? Give feedback.
-
|
I am experiencing the same warning:
This warning appears in a brand new Mac mini. The details are as follows:
I have the same setup in my MacBook Pro with the same version numbers, and I do not see this warning there. Edit: I did a bit of digging and found that for some reason the cask |
Beta Was this translation helpful? Give feedback.
-
|
I don't have |
Beta Was this translation helpful? Give feedback.
-
|
Same error for me on a fresh install of macos 15.1: |
Beta Was this translation helpful? Give feedback.
-
|
Ran into the same issue, reinstall via 'brew reinstall eudic' error. |
Beta Was this translation helpful? Give feedback.
-
|
It works fine the second attempt, that means for each app for each new version need to run |
Beta Was this translation helpful? Give feedback.
-
|
You appear to be on ARM but I'm on x64 and get: |
Beta Was this translation helpful? Give feedback.
-
|
Is there a fix for this? |
Beta Was this translation helpful? Give feedback.
-
|
Edit: My problem appears to have been coincident, but possibly unrelated. I was attempting to install an app through Homebrew, and kept encountering failures ending with this line:
Googling that lead me to this thread. Some time after seeing this thread, I happened upon the App Management pane, which solved my problem, so I left the below suggestion here. Now though, it appears that my issue might have been somewhat unrelated? ( Previously: Everyone, make sure the terminal you are running the brew commands from is in the App Management permissions list in Privacy and Security. This fixed my similar issue. |
Beta Was this translation helpful? Give feedback.
-
|
Hi you mean add Homebrew app to this items?
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @adiputra22 , do you mean a GUI app for Homebrew? If so, I am not aware of the existence of an app like that. I am talking about the terminal itself that you run the |
Beta Was this translation helpful? Give feedback.
-
|
I've added '/opt/homebrew/bin/brew' to App Management, but it still prompts a problem. After running 'brew doctor', a warning will still be displayed: After running 'brew reinstall eudic', an error is returned: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @asins, no not the
Edit: This seems to be a separate issue. See @Cueball's comment here. |
Beta Was this translation helpful? Give feedback.
-
|
The terminal that runs the brew command is Alacritty, which has been appended in my screenshot. |
Beta Was this translation helpful? Give feedback.
-
|
Most cases of this issue can be attributed to some sort of flawed patch in OCLP for Sequoia. I've updated two machines now (MacMini6,1 and MBP6,1) from Sonoma to Sequoia. Checked before upgrading 2nd machine, saw no issues on Sonoma but immediately saw this issue after installation of 15.1.1 Easiest test case is this:
If dev tools/Swift functions correctly, everything in that array up to the "--" gets stripped out, leaving just Have asked friends and colleagues to check on non-OCLP machines (both Intel and AS); no issues reported. CLT only has been used to provide the demonstrated output above, but the issue also arises if only Xcode is installed (paths are obviously slightly different). Would report to OCLP devs, but don't have Reddit anymore, can't get Discord and Github is still closed (thanks to Putler). FTR the "App Management" change might fix a similar problem, but I've just enabled it before writing this; no dice. |
Beta Was this translation helpful? Give feedback.
-
Huh, funky. Seems that there are two concurrent issues that I was mistaking for one, then. Enabling the App Management solved my initial issue (not being able to install an app), but I still have the same other issue you are reporting. |
Beta Was this translation helpful? Give feedback.
-
|
The following command resolve the issue in my case: |
Beta Was this translation helpful? Give feedback.
-
|
Now at macOS 15.2 OpenCoreLegacyPatcher. Tried the three commands but the warning is persisting. When executing the second command seeing this: |
Beta Was this translation helpful? Give feedback.
-
|
The "fix" above will only work if your root cause is a flawed dev tools installation, and is probably unrelated to OCLP. Again, there seems to be multiple causes of the original warning message - some related to OCLP, some not. If the root cause is from OCLP causing issues with your dev tools, you can verify this with the one-line command I posted above. |
Beta Was this translation helpful? Give feedback.
-
|
Please note that devices using OCLP are not supported: https://docs.brew.sh/Installation#macos-requirements |
Beta Was this translation helpful? Give feedback.
-
|
Yep - I suspect most folks using OCLP are (or should be!) aware of that, especially given the recent addition of the "messaging" added in 2c20e3b That said, the
IMHO all the above discussion seems to be consistent with the other proscriptions mentioned by |
Beta Was this translation helpful? Give feedback.
-
Worked for me. On 15.1.1 with a pretty vanilla system (mini, 2018). |
Beta Was this translation helpful? Give feedback.
-
|
The warning was silenced after installing the Xcode app. |
Beta Was this translation helpful? Give feedback.
and others
-
Output of
brew configOutput of
brew doctorDescription of issue
The command
brew doctorsays:I haven't been able to find any relevant information on how to resolve this issue (Google returns like 5 irrelevant results). Because I need an empty output of the doctor command to create a new issue in the Brew repository, it's blocking me from creating new issues. And I just need to create one.
Is anyone able to help me with this issue, please?
Beta Was this translation helpful? Give feedback.
All reactions