brettpoole / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

growlNotificationTimedOut: being sent to delegate with nil clickContext #518

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.  Happens in Growl 2.0beta 3 SDK on Mountain Lion.  Growl 1.2.2 installed but 
not running, so Growl SDK uses notification center.  NOTE: the issue ONLY 
happens when Growl SDK posts to NC.

2.  Invoke a notification like:

    [GrowlApplicationBridge notifyWithTitle:title
                                description:nil
                           notificationName:notificationType
                                   iconData:imgData
                                   priority:0 /* how high of priority the alert is, 0 is default */
                                   isSticky:NO /* indicates if we want the alert to stay on screen till clicked */
                               clickContext:nil]; /* click context is the method we want called when the alert is clicked, nil for none */

3.  Sometimes (not all the time), [GrowlApplicationBridgeDelegate 
growlNotificationTimedOut:] will be called, which causes a crash because I'm 
not expecting it to be called.

What is the expected output?

[GrowlApplicationBridgeDelegate growlNotificationTimedOut:] should never be 
invoked when notification is made with nil clickContext.

Again, when Growl is running, then the SDK does things correctly.  This is only 
an issue when the framework posts to NC in 10.8.  Also, the issue is sporadic 
(but easily reproducible for me).

Original issue reported on code.google.com by vishal.k...@gmail.com on 7 Aug 2012 at 11:37

GoogleCodeExporter commented 8 years ago
This will be fixed for Growl 2.0 SDK, its not in the current beta, but I 
checked in the check that makes sure we have a click context before calling 
those methods today.
Closing as fixed in source as of [fcfdf3dd1bd5]

Original comment by dan...@growl.info on 8 Aug 2012 at 7:32

GoogleCodeExporter commented 8 years ago
Growl 2 is released, marking these as fixed.

Original comment by ch...@growl.info on 20 Sep 2012 at 3:16