Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Allope,
I’ve recently bough Flex Builder 3 and I am completely dissatisfied with its reluctance to debug. It manages to debug a few times, but after that, it just doesn’t want to “connect to the debugger”.
Help?
There is no easy fix for this. You now have to join the rest of us waiting for Adobe to update Flex Builder with a fix they say they have.
You can find the long sad story here: http://bugs.adobe.com/jira/browse/FB-16153:
Basically, this is an issue that has been around for months. Adobe says it has a fix – however – they’ve not released that fix yet. Adobe reports it’s a threading issue…
For the rest of us (waiting for this) – if you need to move forward you can:
A) Live with the problem (painful)
1) Note that in the bug text there are several attempts to work around this – sometimes people find ways to soften the issue – but no one reports a full fix
2) Note that people trying the LocalHost fix – sometimes report a gain in productivity – but in most cases they do not.
B) Switch SDKs from 3.2 (or 3.3) to 3.1 —- No one knows why – but it fixes the problem (you can then include the SWFs you need for 3.2 directly
C) Develop on Mac [Not a smart ass answer – honestly – for whatever reason this bug is not on Flex Builder for the Mac]
Join the bug discussion – on Adobe’s site – it’s still active as people are still waiting for the fix.