by ryan » Thu Aug 07, 2014 1:03 pm
I'm afraid an error report wouldn't help as any firewall blocking or interaction is completely external to our application.
Unfortunately the OSX firewall is simply broken as far as I can tell. Our application is signed with an apple certificate - you can verify that it is signed from the command line with the command "codesign -vvv /Applications/Sighthound\ Video.app". If an application is signed all traffic should be automatically allowed. Even if it wasn't signed, or wasn't properly signed, the firewall should be displaying the Allow/Deny popup.
There aren't any special APIs or requests our app can issue to try to talk to the firewall, all we can do is have our application signed or not, and in either case the OSX firewall is still not working properly.
We tried a number of tricks and added the ones that seemed to alleviate issues into version 2.2. I've done most of my personal testing on 10.9.X and 10.10 and I haven't been able to trigger the firewall blocking and we haven't been hearing from users on this issue since the update either. Given the sporadic behavior of the firewall though, I can certainly believe it doesn't work everywhere. We'll continue to look for further workarounds, but this is really an issue on Apple's side.