-
Notifications
You must be signed in to change notification settings - Fork 305
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
Installing from brew won't run due to "Hidden Bar.app" can't be opened because Apple cannot check it for malicious software. #290
Comments
same problem here |
I have same issue, but I could install it with appstore |
You can open it by following the steps below (this has to be done just once)
Taken from here: |
It doesn't work. I installed from Mac App Store. I have tried the |
Works great on Sonoma 14.3 running on M3. |
If the above workaround does not work and you trust the developer, enter in Terminal the following command:
This will remove the quarantine flag that prevents launching the application. If you run Hidden Bar from a different location, just change the path (drag the application on to Terminal window after |
Go to: System preferences -> Security and Privacy -> Unlock settings (icon in left bottom) -> Allow. |
None of these workarounds are working. (The preference window was already opening after I had tried I have given up already and as of now I am not using any menu bar app. (By the way: with caveat that shortcut to toggle feature doesn't work, among all these, Dozer still worked the best). |
Has worked for me now. |
Describe the bug
I'm just reinstalling everying on my machine which has been reimaged by our company to new. I installed hiddenbar from the brew, using
brew install --cask hiddenbar
but I cannot open it.Steps to reproduce
Expected behaviour
The app should open
Screenshots
Environment
You may write here the specifications like the version of the project, operating system, or hardware if applicable.
Smartphone (please complete the following information):
n/a
Logs / Stack trace
The text was updated successfully, but these errors were encountered: