Clicking a notification doesn't bring Adium to the foreground.

[GoogleCodeExporter]

I'm reporting this issue as Chris requested: 
https://groups.google.com/forum/#!topic/growldiscuss/04IMJUBNXAY.

----

= What steps will reproduce the problem? =
(0. Set up Adium to show a Growl notification, for example for a mention of 
your user name in a multi-user chat.)
1. Click a Growl notification with Adium in the background.
2. Notice how that does not bring Adium to the foreground.

= What version of the product are you using? On what operating system? =
Growl 2.1.2 on OS X 10.9.

= Additional info =
- I'm almost 100% sure this worked before updating from OS X 10.8.5 but I 
cannot check as I do not have access to a 10.8 machine as of this moment.
- I haven't tested this with other apps than Adium.

Original issue reported on code.google.com by Robert.V...@gmail.com on 24 Oct 2013 at 10:37

[GoogleCodeExporter]

this is a known issue with frameworks after 1.3 and prior to 3.0. 3.0 had one 
crasher that i encountered after attempting to put it into GrowlMail, which 
resulted in us pulling 3.0 sdk from download until such time as we can address 
the crasher.

Original comment by rarich...@gmail.com on 25 Oct 2013 at 12:01

[GoogleCodeExporter]

Thanks for the speedy response.

So the gist is: wait it out till the Growl 3.0 SDK is stable enough to be 
released and deployed in Adium, right? Is the crash you mention the only 
blocker for the 3.0 release?

Original comment by Robert.V...@gmail.com on 25 Oct 2013 at 12:56

[GoogleCodeExporter]

that is correct, the only known issue with the 3.0 sdk is that one crasher in 
the network code. 

this would largely be resolved if we switched the framework over to ARC, but 
that would mean dropping support for 32-bit apps and i'm not sure we're there 
yet. the reason this would resolve the issue is because the delegate for the 
GCDAsyncSocket is getting released and the socket object's reference isn't 
getting set to nil, so when it finishes the read it tries to message the 
delegate and then crashes.  We forked our version of GCDAsyncSocket prior to 
GCDAsyncSocket going ARC and the previous mentioned 32-bit issue prevents us 
from moving forward with that in a way that we gain bug fixes w/o substantial 
effort.

Original comment by r...@growl.info on 25 Oct 2013 at 10:53

[GoogleCodeExporter]

Having updated to Growl 2.1.3 I can longer reproduce this issue. :-)

Original comment by Robert.V...@gmail.com on 29 Oct 2013 at 8:40

[GoogleCodeExporter]

Original comment by rarich...@gmail.com on 19 Nov 2013 at 5:04

• Added labels: Product-SDK