Can't verify/open on latest macOS

[danispringer]

Before opening the issue, have you...?

• [x] Searched for existing issues
• [X] Updated SlimHUD to the latest version (if applicable)

Describe the bug

Can't verify/open on latest macOS

Steps to reproduce

brew install, double click on app in Applications folder

Expected behavior

launch

Anything else?

No response

Environment Information (please complete the following information)

- macOS version:13.4 (22F66)
- Mac model: M1 Air
- Monitor(s): N/A
- Apple Silicon/M1 (yes or no): yes

[AlexPerathoner]

Are you sure that SlimHud isn't already running? e.g. if you try changing the volume after opening it, does the default macOS hud still get shown? I can see how this behaviour can be quite confusing, which is why I'm working on #116

[danispringer]

Are you sure that SlimHud isn't already running? e.g. if you try changing the volume after opening it, does the default macOS hud still get shown? I can see how this behaviour can be quite confusing, which is why I'm working on #116

Gonna retry on June 5th 😉 Thank you

[aremmell]

There is a similar concern, at least on this version of macOS (13.5 (22G74)) when installing via brew, I get this upon double-clicking the icon from Applications:

In order to get 'round it, you need to hold ⌥ and right-click, choosing Open while still holding the option key down. This will let you bypass the restriction, but you should probably look into why it's happening in the first place.

Perhaps Homebrew just moving the .app file to Applications upsets the OS–or there's some interface you're supposed to implement that's missing ("software needs to be updated..."). I'm not sure.

I looked through Console and didn't find anything relevant, but I did notice that the following messages appear to be spamming on repeat every half second or so:

[AlexPerathoner]

It's probably because I'm not part of the Apple Developer Program anymore. The console logs are weird, though - but unrelated

[malicious]

I'm running SlimHUD 1.5.1 on macOS 13.5, so it's probably signing-relrated.
Fyi on a different system, here's what Apparency shows (with vscode for comparison):

[Zac08]

There is a similar concern, at least on this version of macOS (13.5 (22G74)) when installing via brew, I get this upon double-clicking the icon from Applications:

In order to get 'round it, you need to hold ⌥ and right-click, choosing Open while still holding the option key down. This will let you bypass the restriction, but you should probably look into why it's happening in the first place.

Perhaps Homebrew just moving the .app file to Applications upsets the OS–or there's some interface you're supposed to implement that's missing ("software needs to be updated..."). I'm not sure.

I looked through Console and didn't find anything relevant, but I did notice that the following messages appear to be spamming on repeat every half second or so:

All you need to do In this case is go to: Settings > Accessibility > (then scroll down a bit) then you'll find something that looks a bit like this

Just click open anyway, and you should be good to go :)

[AlexPerathoner]

This is because I'm not part anymore of the Apple Developer Program (99€ per year just to sign this open source app is too much as a student!). Because the automatic update system verifies that the signing of the new version is the same as the old one, I'll propably keep it unsigned even if I should someday get into the program. The alarming message is just Apple trying to scare people off from non-App Store distribution. As @Zac08 pointed out, you can just ignore it by opening it anyway in the System Preferences. Even faster, right click on the app (not double click) > open.