-
Notifications
You must be signed in to change notification settings - Fork 330
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
-open: Click terminal-notification then brings another notification #288
Comments
I'm seeing this too, and it appears to have started after the Big Sur 11.6 update. I know it was working correctly before that. |
I am seeing it too, and like charlottehu111, it only started with Big Sur 11.6. |
I'm having the same issue too, and it was right after I installed Big Sur 11.6. |
I am also having the same issue and I am on Big Sur 11.6. Please fix this soon! |
I'd like to note that in addition to I haven't tried the fix linked above since it's not merged yet, but for anyone hitting this you might want to try replacing
terminal-notifier -title 'my title' -message 'my message' -open 'https://google.com' Then you can replace it with: outcome=$(alerter -title 'my title' -message 'my message')
if [[ $outcome == '@CONTENTCLICKED' ]]; then
open 'https://google.com'
fi |
Hi, is there a posibility/plan to fix this issue? |
Maybe this project should be forked? If I depended on it more, I'd consider doing so myself. But I switched to Alerter when this problem started. |
Sorry I don't own a Mac at the moment (mine died and not sure I'll have the funds for a new one soon). I guess Apple changed their APIs I'll need to look into this but time is an issue for me these days. |
johnlee999's pull request above fixed the issue for me. |
Thx for your replys! |
Clicking the notification works again for me after upgrading to macOS Monterey. |
It also works correctly again with Big Sur 11.6.1. |
Please check everything that applies to your issue:
To help us debug your issue please include:
macOS big Sur
2.0.0
homebrew
Hope someone help me with this issue...
Common issues and solution:
Thanks!
The text was updated successfully, but these errors were encountered: