This is happening on a Mac OSX environment: I'm discovering that from time to time the cache in Firefox causes the debugger in Flex Builder to behave abnormally. It seems that Firefox retrieves a copy of the debug output SWF from its internal cache rather than loading it fresh from the output folder.
This behavior causes issues when a new debug build is being debugged and is most visible when breakpoints in Flex Builder all of a sudden state that there is no code at that location. I've run into this issue now a few times and most recently couldn't figure out why my code wasn't returning the correct data type for a service call. Turned out that the Flex debugger was working with an outdated (pulled from Firefox cache) version of the application and therefore was returning the wrong data type based on old code. Once the cache was cleared, everything operated normally and as expected. Has this problem been documented and other than not allowing Firefox to cache the content, has anyone found a resolution to this? Thanks, Jurgen
