growlnotify doesn't work in 1.3

[phill]

Along with many other programs growlnotify has stopped working for me
since 'upgrading' to 1.3.
I'm using growlnotify installed from 1.2.2, any suggestions how I can
get this working again?

Will there be 'Extras' for 1.3?

[rudders]

Same issue here;

console log reports

Oct 5 15:28:46 MacBook-Air Growl[231]: Dispatching notification from
growlnotify: Command-Line Growl Notification
Oct 5 15:28:46 MacBook-Air Growl[231]: Never heard of this app!

[sulo]

similar problem here. it works only for one app
http://cl.ly/1G1B0d3L1q3J0x150h3L

expected to be working for iTunes, Mail, Adium, HardwareGrowl ..

was happy to pay, but only frustration and dissapointment

[Watts Martin]

The problem appears to be two-fold:

(1) growlnotify can't register itself with the new Growl, so messages
are rejected.

(2) Notifications *must* be named correctly to be passed, or Growl
reports that the user didn't authorize them. Growl 1.3 treats all
notifications from growlnotify as "Command-Line Growl Notification,"
so that's the one and only notification that you must enable.

You can re-enable the command line app by running this AppleScript in
AppleScript Editor:

tell application "Growl"
set allNotifications to {"Command-Line Growl Notification"}
register as application "GrowlNotify" all notifications
allNotifications default notifications allNotifications icon of
application "Terminal.app"
end tell

Then, you can run a command with something like:

growlnotify -m 'My message' -n 'GrowlNotify' 'Title'

The parameter to -n *must* match the application name in the
AppleScript (register as application "Name") or the notification won't
be sent. Theoretically, you could register growlnotify under multiple
application names, but I don't think it gets you anything. Also note
that the new history function uses the 'Title' parameter for its
headings, so while growlnotify doesn't require title to be set, your
history will be full of blank lines if you don't use it.

This is not precisely a bug, but growlnotify really needs to be
updated to execute these commands for a user.

[Mark Burgess]

I tried this and keep getting the following error:

error "Growl got an error: Exception raised while processing: -[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: ApplicationIcon)" number 1

Any ideas?  Thanks!

[Dave Lewis]

On Oct 5, 3:11 pm, Watts Martin <lay...@gmail.com> wrote:
> You can re-enable the command line app by running this AppleScript in
> AppleScript Editor:
>
> tell application "Growl"
>         set allNotifications to {"Command-Line Growl Notification"}
>         register as application "GrowlNotify" all notifications
> allNotifications default notifications allNotifications icon of
> application "Terminal.app"
> end tell
>
> Then, you can run a command with something like:
>
> growlnotify -m 'My message' -n 'GrowlNotify' 'Title'
>
> The parameter to -n *must* match the application name in the
> AppleScript (register as application "Name") or the notification won't
> be sent. Theoretically, you could register growlnotify under multiple
> application names, but I don't think it gets you anything. Also note
> that the new history function uses the 'Title' parameter for its
> headings, so while growlnotify doesn't require title to be set, your
> history will be full of blank lines if you don't use it.
>
> This is not precisely a bug, but growlnotify really needs to be
> updated to execute these commands for a user.

Thank you so much! This fixed growlnotify for me. I did not ever
have prior versions of Growl installed under Lion, I'm not sure if
that's why it worked for me but not others.

[Watts Martin]

On Oct 5, 12:56 pm, Mark Burgess <ima...@gmail.com> wrote:
> I tried this and keep getting the following error:
>

> *error* "Growl got an error: Exception raised while processing:

> -[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key:
> ApplicationIcon)" number 1
>
> Any ideas?  Thanks!

Hmm. Not any really good ideas. That sounds like an issue with trying
to set the application icon (assuming I'm reading the error right),
but I don't know why that would raise a Cocoa exception. Make sure
you've spelled "Terminal.app" right? Possibly a stupid suggestion, but
it's the only one that comes to mind immediately. :)

[Christopher Forsythe]

We're about to start beta testing growlnotify for 1.3. This will be a short beta period, since it's not going to get a localization change or anything like that.

Chris 

[Watts Martin]

On Oct 5, 3:46 pm, Christopher Forsythe <ch...@growl.info> wrote:

> We're about to start beta testing growlnotify for 1.3. This will be a short
> beta period, since it's not going to get a localization change or anything
> like that.

Cool. This didn't come across as an "everything needs to be rewritten"
kind of problem, so I expected an update to come along shortly. I'm
just being impatient and trying to find ways to jump the gun. :)

[Christopher Forsythe]

If you want, find a gntp implementation that'll replace the functionality for now. :)

Chris

 

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

[George C]

I'm seeing the exact same error in the AppleScript Editor event log
when attempting to run a Growl notification via AppleScript. The odd
thing is that it was just working fine an hour ago. I've tried
multiple app names for the icon and get the same error each time.

When I run via the command line using growlnotify, it pulls the app
icon without a problem. I am only seeing this error when running via
AppleScript.

On Oct 5, 3:56 pm, Mark Burgess <ima...@gmail.com> wrote:
> I tried this and keep getting the following error:
>

> *error* "Growl got an error: Exception raised while processing:

[George C]

Is there any update to this issue from the developers? Very
frustrating as I had Growl in quite a bunch of AppleScripts, all of
which are now crippled until this is fixed.

[Chris Forsythe]

Which version of growlnotify are you using?