Jump to content

Banner Be Gone — Close notification alerts


Recommended Posts

Posted

How to Report Issues

 

Accurate and thorough information is crucial for a proper diagnosis. At a minimum, your report should include:

  • The debugger output of the failing action.
  • Your installed versions of: the Workflow, Alfred, and macOS. Be precise, don’t say “latest”.

More information is always welcome. A short video of the steps with the debugger open may help to identify the problem faster.

  • 3 months later...
Posted

I love this workflow! However, it doesn't quite dismiss all notifications. For example, if I have a Slack notification, instead of closing the notification, it toggles the reply state of the notification (which allows a quick reply to the Slack message). 

 

I updated the code in the workflow to run banner.perform() twice and that usually dismissed everything.

 

However, that probably isn't the best way to do it. 

 

Thanks!

 

Posted

Thank you for the kind words.


Due to the nature of the operation, the alternative would be to check all possible actions on every banner then perform on the one whose name indicates it closes the notification. However, that is considerably slower and it would require getting the names of the Close and Clear All operations in every language, which either requires configuration or becoming even slower. I spent a ton of time on that.


In other words, there’s always a trade-off. I picked the least annoying one. Maybe you can change Slack’s notification type to be different?

  • 2 weeks later...
Posted

Thanks for the workflow. But I'm getting error message; running on latest Alfred and MacOS.

 

ERROR: Banner Be Gone[Run Script] /Users/mac1/Library/Caches/com.runningwithcrayons.Alfred/Workflow Scripts/47616846-5A63-432A-B974-55E7749E5800: execution error: Error: Error: Invalid index. (-1719)

Posted
1 minute ago, Stephen_C said:

It's probably helpful to paste the entire debugger output in case that helps in diagnosing the specific problem.

 

Stephen

it's only 1 liner. Not other message

Posted
9 hours ago, iApple said:

running on latest Alfred and MacOS.

 

Please always share the exact version. Developers are often on different releases from users and “latest” is fuzzy (latest beta, stable, pre-release?). Plus, it makes it harder for others who arrive later to identify if the issue applies to them. To provide informed help it is imperative that we work with precise information.


Also, for this I’ll need a screen recording of it happening, with the debugger open.

  • 4 weeks later...
Posted (edited)

workflow version: 2023.2

 

```

[15:02:32.566] Logging Started...
[15:02:36.122] Banner Be Gone[Keyword] Processing complete
[15:02:36.128] Banner Be Gone[Keyword] Passing output '' to Run Script
[15:02:36.293] ERROR: Banner Be Gone[Run Script] /Users/<USER>/Library/Caches/com.runningwithcrayons.Alfred/Workflow Scripts/7DCFD641-6A1E-4799-B550-AF03A71B2800: execution error: Error: Error: Invalid index. (-1719)

```

 

screen recording https://www.dropbox.com/scl/fi/wdr3dpyaee3a8mhwqeei9/video.mp4?rlkey=q0v7v77s3cjn2479nmrbvj4zw&dl=0

 

@vitor Any way to fix this?

Edited by andy4222
  • 4 months later...
Posted

Vitor -- just wanted to thank you for this workflow. It is one of my most used and it is a great example of something that does one thing extremely well. I rely on certain notifications daily and therefore have them set to be Alerts so they remain until i dismiss them with Banner Be Gone! 

  • 2 months later...
  • 2 weeks later...
Posted

I am on Sequoia Beta 15.1 and I have v2024.2 installed and this workflow does not work for me. Previously, it was working before I updated to Sequoia. I also tried 2024.1 and that did not work either on Sequoia. Does it not work with the Beta version?

Posted

Thank you Stephen_C for linking those resources to me.

I am having an issue with bannerbegone v2024.2.

Here are some details:

How I ran the workflow: typed "bannerbegone" in the alfred search bar and hit enter to use the workflow
I have attached an image of the output from the debugger
bannerbegone.png.c74d9d15720ed75fab57b9798fe124bc.png
Workflow version is v2024.2
Alfred version is 5.5.1
MacOS version is Sequoia Beta 15.1

Posted

It's actually better to copy and paste the entire output of the debugger: that is likely to be more helpful in tracking the actual problem.

 

Stephen

Posted

@dav What @Stephen_C said is correct. A screenshot of part of the debugger doesn’t reveal much. My workflows always have at the top (the second post) how to properly report bugs.

 

I’ll take a look when 15.1 is stable. It’s weird that Apple would’ve changed this in a point release when it was just modified. 15.0 and 15.1 were developed in tandem so whatever’s happening is likely to have resolved itself by then. Tackling this right now would likely mean spending multiple hours on a wild goose chase and then throwing all the effort away.

  • 4 weeks later...
Posted

Updated to 2024.4.

  • Use Automation Task to get macOS version.
  • Update Sequoia support to Sequoia 15.1. Yes, Apple changed notifications again. There’s little reason to not update to 15.1 if you’re already on Sequoia and forking on the same major version starts to get complicated, so this one doesn’t add support for the previous version. If you update by mistake before updating your Mac, you can go back to the previous workflow version.
  • 1 month later...
  • 3 weeks later...
Posted

Updated to 2024.6.


Updated for macOS Sequoia 15.2. I have no idea why developers at Apple find it a good use of time to keep tweaking on every point release how notifications display, but here we are. Not keeping support for 15.1, as per before.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...