-
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
[INFO] macOS Big Sur 11.0 beta reports & issues #283
Comments
The |
After explicitly allowing the notifications on BigSur (Click on options after each notification), the sounds works! |
I met same problem but solved it. It works fine when specified the old sound name. e.g.
The corresponding sound names here: https://www.youtube.com/watch?v=XqjifWtmQqQ |
You can find the names for the OS sounds in |
Any update with appIcon? I am on bigSur and I can not seem to get the icon to work terminal-notifier -title ProjectX -subtitle "new tag detected" -message "Finished" -appIcon http://vjeantet.fr/images/logo.png |
There seems no good alternatives icon API for big sur (searched other open source projects as well, same issue), it seems big sur can only use pre-baked assets files as the icon. So I guess |
Could you please elaborate on this? [EDIT] I tried changing filenames as well as the Terminal.icns file in terminal-notifier.app/Contents/Resources to no sucess; also tried changing the package.json name and run npm install but I don't think that's how you did it! |
same as @F3n67u 😢 |
I installed terminal-notifier via brew so there is no .app folder to modify. Am I supposed to install it differently? I am getting this result for the icon too (Ventura): |
Experiencing the identical issue as @frakman1. I notice that by default I end up with the same icon when using the terminal-notifier. If I use the '-appIcon' argument , it doesn't work. However, I do notice the -contentImage will work with an external URL, but for internal images. I am currently using Monterey v12.5. Otherwise all other features seem to work for me. I also used homebrew to install this application as well. |
Here's what I use to fix the broken app icon:
This definitely works on Monterey, but I'm not sure about Ventura. (Note: when running the code signing command, you may need to tweak the path to your local |
@mokolabs Didn't work on ventura. How do you remove from notification pane? I can only disable it. And it didn't work. Any idea ? |
@khurshid-alam I don't know about Ventura, but it's working for me on Sequoia. |
terminal-notifier: 2.0.0
macOS: Big Sur 11.0 Public Beta 6
(1)
-execute
is working fine, it seems(2)
-appIcon
is not working, which was to be expected, because "it relies on a private method"; hope you'll get that working again in the next update(3)
The
-title
option doesn't override the bundle name anymore. Before you just added-title="Title"
, and it overrode the "terminal-notifier" titleIn Big Sur you have an additional header in the notification float denoting not the process name, but the basename of the app bundle:
Maybe there is also a "private method" to change this, but if you change the basename
terminal-notifier.app
for something else, it works:So this would definitely work for nested copies of terminal-notifier, e.g. in a Platypus or Automator app, which also means that we now have four, not three lines of text to print information to the user.
If you change terminal-app's icon, that will (as before) work too. So for nested instances of terminal-notifier, or dedicated standalone instances of terminal-notifier, you can just change icons + Bundle IDs + app basenames, and you're good to go.
But it would be great to have something like an
-appName
argument alongside-appIcon
to implement this for generic copies of terminal-notifier as well.The text was updated successfully, but these errors were encountered: