Question

I have this very strange problem on a big flex app where it would run fine with the debug swf if the user has debug flash installed but will have some disparities for people with standard version of flash.

These disparities include:

• No pop ups

• loose all event catching

• Weird positioning of a button

I read somewhere that updatedisplaylist was handled differently ?
For now i will try the export release way instead of the bin-debug swf, and to go back in the commits to see what was the turning point.

Any similar experiences ?

Answer 1

I’ve been using Flex for a long time and have never heard of any problems like these being related to using the debug vs standard versions of the Flash player, but I have experienced problems similar to what you’re experiencing.

When an exception occurs in your application, like attempting to access something in a null class or trying to access element 10 in an array that only has 9, the debug player will pop up a window stating that an exception has occurred and give you a stack trace, even if you’re not actively debugging the app. The standard player does not, so the user will have no way of knowing that something went wrong.

In my experience after an uncaught exception occurs it can make all running code from that point on very unstable, causing all of the problems you list and more.

I doubt your problem has anything to do with the two different players beyond the standard one not giving you any feedback about the state of your app.