2.1 Breaks "Show Growl Notification" Action

[james.f....@icloud.com]

I have a fairly simple Automator service that has been working perfectly with the "Show Growl Notification" action at the end, until I updated Growl to version 2.1. Now, when I try to run the action, I get an error message about the action being incompatible. Also, when I open the service in Automator, the action is shown as incompatible. When I delete the action and try to add it again, I get an error message that the action is incompatible. The only thing I changed was the update to 2.1.

I am running Mountain Lion, which is fully up to date.

[Chris Forsythe]

We've confirmed this is a problem. We'll get a fix out soon. 

--
Chris Forsythe

On Wednesday, July 31, 2013 at 10:03 PM, james.f....@icloud.com wrote:

I have a fairly simple Automator service that has been working perfectly with the "Show Growl Notification" action at the end, until I updated Growl to version 2.1. Now, when I try to run the action, I get an error message about the action being incompatible. Also, when I open the service in Automator, the action is shown as incompatible. When I delete the action and try to add it again, I get an error message that the action is incompatible. The only thing I changed was the update to 2.1.

I am running Mountain Lion, which is fully up to date.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to growldiscuss...@googlegroups.com.
To post to this group, send email to growld...@googlegroups.com.
Visit this group at http://groups.google.com/group/growldiscuss.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[HD Schellnack]

Same here - after the Update from MAS that I did today (2nd Aug). 

Basically broke all of my Automator-Actions that end up with a Growl-Display.  

[Chris Forsythe]

We could use one or two beta testers to help test the Automator action. Please email me if interested ch...@growl.info

--
Chris Forsythe

On Friday, August 2, 2013 at 4:18 AM, HD Schellnack wrote:

Same here - after the Update from MAS that I did today (2nd Aug). 

Basically broke all of my Automator-Actions that end up with a Growl-Display.  

--

[stephy rul]

interested

You received this message because you are subscribed to a topic in the Google Groups "Growl Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/growldiscuss/HfSkTnaraHA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to growldiscuss...@googlegroups.com.

[roar]

On Saturday, August 3, 2013 at 9:05:46 PM UTC+2, Christopher Forsythe wrote:

We could use one or two beta testers to help test the Automator action. Please email me if interested ch...@growl.info

On Friday, August 2, 2013 at 4:18 AM, HD Schellnack wrote:

Same here - after the Update from MAS that I did today (2nd Aug). 

Basically broke all of my Automator-Actions that end up with a Growl-Display. 

I'm reusing some old automator actions that fail on the Growl action because apparently it cannot detect that Growl is running. Has it ever been patched?

[Christopher Forsythe]

If it's old then the action may be attempting to call GrowlHelperApp and not Growl. I honestly don't know off the top of my head though.

--

Chris Forsythe

[roar]

On Monday, February 13, 2017 at 5:35:54 PM UTC+1, Christopher Forsythe wrote:

If it's old then the action may be attempting to call GrowlHelperApp and not Growl. I honestly don't know off the top of my head though.

The bundle identifier in Growl.app v2.1.3 is still com.Growl.GrowlHelperApp. Before I posted I did re-save the services that contained the Show Growl Notification actions, but somehow it didn't work. I tried this again and now it's working, although in the meantime I reset the launch services db, if that has anything to do with it.