Hi, my name is Timo Ernst and I am a web expert.

Google Chrome Flash debugger not connecting to Flex/Flash Builder?

Posted on: April 14th, 2010 by Timo

If your Flex/Flash Builder has suddenly problems connecting to your Flash debugger, you might be using Google Chrome.

It seems like Google started bundling the Flash Player together with Chrome, which has an automatic updating engine (in the background) and thus you probably didn’t notice the update. This integrated version of Flash Player is the standard version of the plug-in and not the debugger version. Hence, whenever you view Flash content through Google Chrome, the used runtime is not the one you installed on your local operating system.

Currently, there are two workarounds for this:

  1. Manually replace the Chrome Flash player with the debugger version (Thanks to Josh for the how-to).
  2. Use a different browser for testing your Flash applications in.

Workaround #1

Follow these steps:

  1. Go to chrome://plugins
  2. (For Google Chrome version 6.x and higher only: Click the “details” link in the top right corner.)
  3. Find the entries that say “Flash”.
  4. On Windows 7, deactivate the entry, which has the following path:

    $HOME/AppData/Local/Google/Chrome/Application/chrome_version/gcswf32.dll

    On MacOS X, the path is:

    /Applications/Google Chrome.app/Contents/Versions/chrome_version/Flash Player Plugin for Chrome.plugin

    This will disable the integrated Flash Player bundled with Google Chrome. Watch out not to disable your operating system’s default Flash Player (debugger). You can see the difference in the installation path: The global Flash Player is not installed into a directory associated with Chrome.

workaround #2

In Flex/Flash Builder (or Eclipse), simply go to Preferences -> General -> Web Browser and hit “Use external Web Browser“. Then pick Safari, Firefox or whatever you prefer. This choice will then be your “development test browser”, while you can use Chrome for your daily surfing needs.

TwitterFacebookShare
Tags: , , , , ,

45 Responses

  1. Josh says:

    Just having the same problems and couldn’t figure out what was wrong. Thanks for your post! I’ve found a third option which should be maintained across updates…

    If you go to chrome://plugins/ and disable the C:\Users\[Your Name]\AppData\Local\Google\Chrome\Application\5.0.375.3\gcswf32.dll version of the Shockwave Flash it then seems to use the debug version of the plugin if you have it installed.

    Hope that helps someone!
    Josh

    Thumb up 2 Thumb down 0

  2. Timo says:

    Hey, thanks for that hint :-)
    I’ll put that right into the blog post.

    Thumb up 1 Thumb down 0

  3. Marcel says:

    Disabling the plugin works perfectly! Thnx.

    Thumb up 0 Thumb down 0

  4. steve says:

    Yes! Thank you, Timo.

    Thumb up 0 Thumb down 0

  5. Jeff says:

    Thank you! I was frustrated after re-installing debug version and this still not working

    Thumb up 0 Thumb down 0

  6. Doug in Paia says:

    Wowza! Thanks for this. Very helpful. This issue cost me an hour yesterday. Woke up this morning to this post. Thanks!

    Thumb up 0 Thumb down 0

  7. Timo says:

    No prob, you guys are welcome ;-)
    Chrome’s updating engine really can be a bit nasty sometimes.

    Thumb up 0 Thumb down 0

  8. ronnie says:

    yay!
    been looking for the answer for quite a while – thanks for this one!!

    :)

    Thumb up 0 Thumb down 0

  9. [...] chrome-flash-debugger-not-connecting-to-flexflash-builder/ [...]

    Thumb up 0 Thumb down 1

  10. Nils says:

    Bless you! I had just upgraded my OS and installed everything again and couldn’t figure out what was wrong. Thanks so much!

    Thumb up 0 Thumb down 0

  11. [...] 原文链接:http://www.timo-ernst.net/2010/04/chrome-flash-debugger-not-connecting-to-flexflash-builder/ 本文固定链接: http://blog.syanix.com/?p=358 | Yoh’s WebSphere [...]

    Thumb up 0 Thumb down 0

  12. Dawid says:

    big +
    :)

    Thumb up 0 Thumb down 0

  13. JRW says:

    Nice – thanks

    Thumb up 0 Thumb down 0

  14. Sean says:

    Disabling the Chrome plugin works like a charm.

    Many thanks

    Thumb up 0 Thumb down 0

  15. Pete says:

    Disabling the Chrome plugin worked perfectly. Thanks for the help.

    Thumb up 0 Thumb down 0

  16. georgemck says:

    we really need to test on multiple browsers..
    gratzi

    Thumb up 0 Thumb down 0

  17. Gaurav says:

    Saviour!!

    Thumb up 0 Thumb down 0

  18. Adam Szecowka says:

    Thank you!

    Thumb up 0 Thumb down 0

  19. Senthil Raj says:

    Thank you!

    Thumb up 0 Thumb down 0

  20. Elliot says:

    Perfect, thanks.

    Thumb up 0 Thumb down 0

  21. Nomad says:

    A big thanks to you! I can finally debug using chrome..

    Thumb up 0 Thumb down 0

  22. Ofir says:

    Great post. Thank you. You saved my hours of frustrations …

    Thumb up 0 Thumb down 0

  23. Thomas says:

    Awesome! Thanks for posting this!

    Thumb up 0 Thumb down 0

  24. lacroix says:

    same problem with flashbuilder but no google chrome installed :( (((
    Windows 7 with CS5 (Flashbuilder 4)and FlashPlayer 10. Always breaks up at 57% when starting debugging….nothing helps (everthing completly new installed)….flash player cant connect to debugger….using firefox :(

    Thumb up 0 Thumb down 0

  25. Timo says:

    @lacroix
    Hey, you said that you are using Flash Player 10.
    That’s wrong.
    You must uninstall that and install the Flash Player CONTENT DEBUGGER instead: http://www.adobe.com/support/flashplayer/downloads.html

    Thumb up 0 Thumb down 0

  26. Dieter says:

    Nice! Rock On !

    Thumb up 0 Thumb down 0

  27. Arvind says:

    Thanks for the help.
    I disbled the ‘gcswf32.dll’ line and debugger option is working :-)

    Thumb up 0 Thumb down 0

  28. mc200 says:

    Grazie! Grazie! Grazie!
    Il tuo post mi ha ripagato delle ore di frustrazine spese per trovare una soluzione! :)

    Thumb up 0 Thumb down 0

  29. Anonymous says:

    God bless you!

    Thumb up 0 Thumb down 0

  30. Damien Ivan says:

    Oh dear lord, thank you so much. I was having one of those domino-effect problems and the fact that the debugger wasn’t working was just the top problem on my stack of issues.

    Thanks!

    Thumb up 0 Thumb down 0

  31. [...] player com o debugger embutido. Como o chrome tem alguns problemas de compatibilidade (ver esse post) , vamos fazer esse exemplo para o debug funcionar no [...]

    Thumb up 0 Thumb down 0

  32. unknown says:

    THANK YOU VERY MUCHM, EASY AND STRAIGHT.

    I was searching for solutions in other webpages and some said to change the compiler comand, others said to change some config files…I mean come on! Is there anything easier than this.

    Thank YOU VERY MUCH :)

    Thumb up 0 Thumb down 0

  33. Anonymous says:

    Ok it works perfectly, thanks a lot !

    Thumb up 0 Thumb down 0

  34. Val says:

    ur the man! never would have figured it out on my own

    Thumb up 0 Thumb down 0

  35. AS3developer says:

    Thanks for the solution..

    Thumb up 0 Thumb down 0

  36. satish says:

    Thanks It’s Working

    Thumb up 0 Thumb down 0

  37. Daniel Bae says:

    thank for your post.

    Thumb up 0 Thumb down 0

  38. [...] Perhaps this link is the issue: Chrome default browser fix [...]

    Thumb up 0 Thumb down 0

  39. Thanks a million!

    Simon

    Thumb up 0 Thumb down 0

  40. Jaskaran says:

    Hi Timo,

    Thanks alot. I can now run my flex code in Chrome after diabling chrome’s flash player.

    But when i distribute this flex code to my client i can not ask them to do the same.
    How will this work correctly for release versions..
    Thanks alot
    Jaskaran

    Thumb up 0 Thumb down 0

  41. Timo says:

    @Jaskaran Why would you want your client to run your application using the debug version?

    Thumb up 1 Thumb down 0

  42. Jaskaran says:

    Hi Timo, Thanks alot for replying.
    I deployed my application on the server, then i didnt face any issue in chrome.
    I didnt know that if you run flex code locally it runs in debug version on flash.

    Thanks for the information.
    Jaskaran

    Thumb up 0 Thumb down 0

  43. Airgame16 says:

    Ok excelente

    Thumb up 0 Thumb down 0

  44. [...] are ways around this in Chrome if you want to fix it, but I recommend using another browser for debugging purposes.  When I switched my default browser [...]

    Thumb up 0 Thumb down 0

  45. me says:

    awesome, years later and this fixed it for me.

    Thumb up 0 Thumb down 0

Leave a Reply