Comments on: Flex 3 profiling not working (update)

By: Brian

Brian — Thu, 01 Dec 2011 01:14:06 +0000

I had a custom preloader defined in my application. Disabling it worked for me. Stupid mistake, but took me hours to figure it out.

By: Flash Builder profiler error: Unable to connect | Wilson Silva

Flash Builder profiler error: Unable to connect | Wilson Silva — Thu, 29 Sep 2011 15:37:49 +0000

[...] I just unhid the file and it connected. If you’re getting the same error and this workaround does not work for you then take a look at this [...]

By: Ivan Slepchenko

Ivan Slepchenko — Wed, 25 Aug 2010 20:05:41 +0000

removing wmode=”transparent” working for me. This is not a joke!

By: Jack

Jack — Tue, 01 Jun 2010 17:58:02 +0000

Adding the workspace as a trusted location did it for me.

By: How I got it to work

How I got it to work — Tue, 30 Mar 2010 20:57:35 +0000

Hi all,

More than likely the problem has to do with Flash Player security settings. Edit your security settings here:

http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html

Add the root level of your Flash Builder workspace as a ‘trusted’ location. If you were seeing this error in your flash logs:

PreloadSwf paths must be local trusted:

you won’t see it anymore and profiling should work!

By: Jozef Chúťka

Jozef Chúťka — Fri, 22 Jan 2010 22:02:35 +0000

Pedro, does your application use rsl or external modules? Are you able to profile blank new created project?

By: Pedro

Pedro — Fri, 22 Jan 2010 21:25:27 +0000

None of above worked for me.. I miss profilling my app

By: Durairaj

Durairaj — Wed, 13 Jan 2010 21:17:07 +0000

Thanks!! i didnt need to spend much hour like you since you wrote a nice blog which was very helpful to figure out. In my case port was causing problems