Skip to content
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

Open
JayBrown opened this issue Sep 12, 2020 · 15 comments
Open

[INFO] macOS Big Sur 11.0 beta reports & issues #283

JayBrown opened this issue Sep 12, 2020 · 15 comments
Labels

Comments

@JayBrown
Copy link

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" title

snap1

In Big Sur you have an additional header in the notification float denoting not the process name, but the basename of the app bundle:

snap2

Maybe there is also a "private method" to change this, but if you change the basename terminal-notifier.app for something else, it works:

snap3

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.

snap4

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.

@scotow
Copy link

scotow commented Nov 15, 2020

The -sound option doesn't seem to work anymore too. It plays the same (old default) sound no matter what sound name I try to pass.

@helloguille
Copy link

After explicitly allowing the notifications on BigSur (Click on options after each notification), the sounds works!

@shogogg
Copy link

shogogg commented May 5, 2021

The -sound option doesn't seem to work anymore too.

I met same problem but solved it. It works fine when specified the old sound name.

e.g.

# It does not work
terminal-notifier ... -sound Breeze

# It works!!
terminal-notifier ... -sound Blow

The corresponding sound names here: https://www.youtube.com/watch?v=XqjifWtmQqQ

@fmaclen
Copy link
Contributor

fmaclen commented Aug 24, 2021

You can find the names for the OS sounds in /System/Library/Sounds.

@tannerPriest
Copy link

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 

@wilbeibi
Copy link

wilbeibi commented Dec 1, 2021

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 -contentImage might be the only workaround.

@F3n67u
Copy link

F3n67u commented Mar 23, 2022

I am on macOS Monterey. -appIcon don't work either.

image

@chipimix
Copy link

chipimix commented Mar 31, 2022

you can just change icons + Bundle IDs + app basenames, and you're good to go.

Could you please elaborate on this?
Thanks!

[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!
[EDIT x2] Replacing "terminal-notifier" in the "Info.plist" as well as the "notification.js" file did the trick!

@ctf0
Copy link

ctf0 commented Apr 20, 2022

same as @F3n67u 😢

@YunshuaiPeng
Copy link

I am on macOS Monterey. -appIcon don't work either.

image

same issue

@frakman1
Copy link

you can just change icons + Bundle IDs + app basenames, and you're good to go.

Could you please elaborate on this? Thanks!

[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! [EDIT x2] Replacing "terminal-notifier" in the "Info.plist" as well as the "notification.js" file did the trick!

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):

image

@ghost
Copy link

ghost commented Aug 20, 2022

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.

@mokolabs
Copy link

mokolabs commented Jul 3, 2023

Here's what I use to fix the broken app icon:

  • Verify icon is broken:
    echo 'Hello!' | terminal-notifier -sound default
  • Open Notifications preference pane
  • Remove terminal notifier from app list
  • Sign app with ad-hoc signature:
    codesign --sign - --force --deep /opt/homebrew/Cellar/terminal-notifier/2.0.0/terminal-notifier.app
  • Verify icon is fixed:
    echo 'Piped Message Data!' | terminal-notifier -sound default
  • Reopen Notifications preference pane
  • Allow notifications for terminal notifier

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 terminal-notifier binary.)

@khurshid-alam
Copy link

@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 ?

@mokolabs
Copy link

@khurshid-alam I don't know about Ventura, but it's working for me on Sequoia.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests