sorry for the delay. The port 8765 is free and not bound to any interface.
In the security preferences is Flash Builder listed and allowed for incoming
traffic (green point).
After performing a port scan on my own machine it appears port 8765 only opens up after launching Flash Builder and clicking allow each time even though an initial firewall exception is supposedly added on first launch in OS X's GUI based firewall preference pane for Adobe Flash Builder 4.app.
So, even though the exception is added on first launch of FB it does not appear to do anything on allowing an exception on port 8765 as a permanent preference.
It happens with Vuze as well.
I've been having this problem as well, but I've figured out the cause (on my machine, at least) — the signature on the Flash Builder application is invalid. If an application with an invalid signature listens for incoming network connections, the Mac OS X firewall will prompt for permission every time the application launches.
You can check for this yourself using the
codesigncommand-line utility. I was having the same problem with iTunes, and found a support discussion that says you can fix it by reinstalling iTunes (so that its signature still matches the application). Here's what
codesignsays about iTunes now that I've done just that:
codesign -vv /Applications/iTunes.app
/Applications/iTunes.app: valid on disk
/Applications/iTunes.app: satisfies its Designated Requirement
codesignsays about Flash Builder on my machine:
codesign -vv /Applications/Adobe\ Flash\ Builder\ 4/Adobe\ Flash\ Builder\ 4.app
/Applications/Adobe Flash Builder 4/Adobe Flash Builder 4.app: a sealed resource is missing or invalid
/Applications/Adobe Flash Builder 4/Adobe Flash Builder 4.app/Contents/MacOS/Adobe Flash Builder 4.ini: resource modified
I'm going to try reinstalling Flash Builder, to see if that fixes it (and if it stays fixed).
Message was edited by: Mediascape_Josh — edited to (hopefully) be legible this time.
Having this problem as well, anyone ever determine a solution??
One thing that is not a solution is reinstalling Flash Builder — the same problem reappeared almost immediately. I'll have to repeat the whole experiment again to make a useful bug report out of my information, but the damage might have been done by the installer itself (and I think it was a different file that Adobe is corrupting).
There is an ugly workaround for this situation, but I'm hesitant to explain it due to an assortment of possible complications (anyone who knows the system well enough to understand the complications should be able to guess the workaround for themselves).
Thanks everyone for the inputs. I have logged a bug for this -> http://bugs.adobe.com/jira/browse/FB-30237
You can vote for the issue if you feel it has to be fixed, and we might consider it in our coming release.
I'm having this problem with Flash Builder 4.7 (Mac OS X 10.7.5).
It's a regression, so it should be fixed regardless of voting.