I have a problem when running debug in my Flash Builder 4. When i click on the debug button, when it launch i have ERROR 404 showing up in my browser.
I have check the debug folder path and compare it with the browser they are the same. I noticed that the index.html is missing. Then i tried to copy the index.html from my release folder and somehow it run. But the when i run the debug again, it shows the ERROR 404 in my browser. Somehow it deleted the index.html that i copied from the release folder.
Anyone experiencing it?
Hi It's me again. I am trying to debug my application but somehow it pop me this error,
I downloaded and tried to install Adobe Flash player, but then when i tried i still have this error. I check the path and found out that the Flash Player.plugin is in the correct directory. Below is the directory captured image.
Appreciate your help on this.
Just an FYI, for anyone encountering the issue where the debugged sporadically connects to the browser debugger... Download the flash projector (stand alone) debugger. Edit the projects debug settings and in the url to debug change the .html to .swf. Instead of luanching in a browser it will launch in the stand alone flash projected application and connect every time. Happy Coding. For even more awesomeness use HellFire Daemon Compiler... its freaking insane!
make sure you install the flash projector debug version -
windows, for mac -
... that should work...
I ran into the same issue today and found this page while searching for help.
None of the suggestions helped. But there was a suggestion to debug in flash itself. So I opened the .html file from bin-debug in the flash builder itself - basically double click, and it worked in the builder. Now the surprising part is I had not closed the applications I'd started for debug, these were still stuck at 57%. These started opening in my browser with debugger version of flash player!! And it was debugging fine!
Guess the trick is to click on the .html file while the progress bar is stuck at 57% for debugging the application. No clue why this works.. I have tried this 2-3 times and it worked always.
hope this helps someone.
This happens because the Flash Debugger uses sockets and it failing to connect to the flash content in the browser.
I find this happens to me when I accidently delete my debug configuration when I delete the project and recreate it.
Developers tend to forget thta if you delete the project and recreate it it will delete your debug configuration as well.
In my Debugging configuration, the default is to debug it from a html file from your file system, but in almost every case
you want to specify a URL because you want to debug how your flash app will act after being actived from a web server.
If it stuck at 57% just terminate it because it will not connect and check you debig configuration setting
I'm having this exact issue with Flash Builder 4.5.1, flex sdk 4.5.1 and air 2.7
My apps are air apps, they run fine, but can't debug. For a mobile application, i can debug on the mobile device, but not on desktop (emulator).
The error is always debugger can't connect to the application.
This is the error when i kill the app before Flash Builder times out trying to connect, it halts at 57%:
Process terminated without establishing connection to debugger.
Launch command details: "I:\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1\bin\adl.exe" -runtime "I:\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1\runtimes\air\win" -profile mobileDevice -screensize 480x762:480x800 -XscreenDPI 252 -XversionPlatform AND "C:\Users\mia\Adobe Flash Builder 4.5.1\test\bin-debug\test-app.xml" "C:\Users\mia\Adobe Flash Builder 4.5.1\test\bin-debug"
This is the error if i let the process to time out:
The Flash Builder debugger failed to connect to the running application.
1. For in-browser applications, you are running the debugger version of Flash Player.
2. For network debugging on a mobile device, you have a reliable network connection to the device, and port 7935 is open on your machine's firewall.
Device connection help
Flash Player is really got nothing to do here since i'm trying to debug Air apps.
Debugging worked fine with Flex sdk 4.5 and air sdk 2.6.
After updating to air 2.7 and sdk 4.5.1 i couldn't debug any Air app, mobile or not (although i can debug on the mobile device, however it's a pain to always debug on the device, it's just a waste of time)
I'm using windows 7 64b btw
Is there any solution for this?
I have encountered this situation many times in Flash Builder 4.5 and it always seems to occur when, prior to launching the application from the Builder I was using phpadmin (wampserver) and failed to close this application in the browser before staerting the debugger.
The app load hangs at 57% every time.
Window xp sp3
I'm having the exact same problem that pin05h is having - debugging in AIR, Flash Builder hangs at 57%, get the same error message every time, not running phpadmin or wampserver. However, when I debug the application, not only do I have nowhere to right click and say Connect (the window does not appear until the error does), but the error only lasts 3 or 4 seconds.
How do I specify that I want the app to run in the browser? And, if we are using AIR-only features (which I'm not sure I am), how do we fix the debugging issue there? Thanks for working to fix this issue.
Steps to resolve this issue, on window machine
- Go to control panel -> add and remove programs
- Uninstall Flash player 64 Bit and Flash Player 64 Bit Active X Player
- Re-install Flash Player 32-Bit version Debugger player.
- Exit your browers if required and Restart you IDE.
This solved my problem, i hope it solves your problem with the warning message on debug click in the IDE.
If you are using Chrome and the Flash plugin, be sure to disable the build in Flash plugin in Chrome:
- Type in you addressbar about:plugins.
- Click on details (in the upper right corner).
- Scroll to the flash plugin. Here you see two files (if you installed a debug version yourself).
- Disable the build in Flash plugin (which is located inside the chrome install folder).
- Restart Chrome, and start debugging your flash content.
Open the Progress Panel (Window>Show View>Other>Progress) and click any red boxes you see there. What has happened is that FB is still compiling the project, but has already launched the browser window. Since the Browser really couldn't load the swf, which was still compiling, you're just kind of "stuck." Once everything cancels out, close the browser and click the "Run" or "Debug" button again. You should find that this time the file launches right off, as it was compiled last time.
I have the same issue on FB 4.6 when connecting to IE 9.0.8... for a debugging session. Can't get past 57%
Funny thing is - the environment WORKS FINE for many sessions - and then just stops working after a while.
Cleaning the project, restarting FB, killing tasks... all do nothing.
I can't right-click on the application to get the player's context menu (as suggested above), because the app is not yet running! IE just dings the system bell when I try that.
The workaround I've discovered - which works specifically for the situation described above - is to...
Keep an eye on the FB launch progress indicator as you start your debug session, after the blank IE window appears.
If you see it hanging at 57%, rapidly click the cancel and reload icons on the IE browser. The flash movie then loads as expected - still in debug mode.
I had the same problem with a web application in Firefox, FB 4.7, Win 7 64-bit. What worked for me was both of the following:
- run FB as Administrator. (e.g., right-click the icon in the start menu and select Run As Administrator)
- if not running as Administrator, browse to the web application (e.g., go to localhost:8080/MyWebApp, or wherever your app is running). Once the app loads, the debugger kicks in.
I've actually found a couple of scenarios recently where the debugger failed to connect that in retrospect should have been obvious, but weren't up front. These are worth checking for as well:
- Check to make sure your swf is compiled with debug information (if you're working between Flash Builder and Flash Pro, the default when you compile from FP is to leave this information out).
- If you have some sort of process up front to get into the swf (for example you have to log in because you're testing that the credentials are being set properly via flash vars), make sure that the code isn't redirecting to a different location than you thought. I recently brought down code to localhost that someone else had written, and I couldn't figure out why the debugger wouldn't connect. It was because the code was hard-coded to launch a swf on the server which, you guessed it, had been compiled without debug info.