Couldn't decipher homebrew response - when viewing taps in Cork.app
Clicking on any of the items in the 'Added taps' section of the Cork.app sidebar results in the message "Couldn't decipher Homebrew response The operation couldn't be completed. (Cork.JSONParsingError error 1.)
- macOS version: 14.5
- Cork Version: 1.4.4. (70)
- Did you compile Cork yourself?: No. We are using the pre-compiled binary from github.com/buresdv/Cork/releases
- Homebrew 4.3.10 installed via the .pkg from github.com/Homebrew/brew/releases/download/4.3.10/Homebrew-4.3.10.pkg
Can you please do which brew in the Terminal? Just to make sure that the executable is in the correct location.
Interestingly, even after reinstalling homebrew from the .pkg which brew reports brew not found in the terminal!
I'm very new to homebrew and don't know much about it's underpinning but I will note that I seem to have a fully populated folder at opt/homebrew...
That's interesting indeed. I have Homebrew installed through the Terminal, and it may be that Homebrew is not in the $PATH. While this should not affect Cork, it's one point of divergence between our systems.
Would it be too much trouble to install Homebrew through the Terminal?
If you'd be up for it, you can uninstall Homebrew using /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)", and then install it again using /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
I will try the CLI uninstall/re-install and report back in a while!
So, it looks like I'm not cool enough to join the homebrew club. I've actually always known this which is why i had hoped that maybe the .pkg installer and Cork.app GUI might help me sneak in. Alas, my attempt to run the uninstall command failed because my user account is not an admin and cannot sudo. When I logged-in with an admin account the response from the uninstall command was that no homebrew was found. So, I guess my issue isn't really a Cork.app bug but a user problem...
the response from the uninstall command was that no homebrew was found.
In that case, I think you can just run the install command and it won't break anything.
Don't worry, this is fixable 😊
Closed due to inactivity