Some ideas:
- compile the app with -verbose-stacktraces=true
- get them to install the debug player… it'll show a dialog when an error
occurs
- or you could trap the uncaughtErrorEvent and display a message (
http://stackoverflow.com/a/6597046/3384609)
Sometimes a null pointer in flex's validation methods (updateDisplayList,
commitProperties) can cause an app to crash.
You can listen for errors on those methods like this.
import mx.core.UIComponentGlobals
import mx.managers.SystemManagerGlobals
import mx.events.DynamicEvent
private function app_preinit(event:Event):void {
UIComponentGlobals.catchCallLaterExceptions = true;
SystemManagerGlobals.topLevelSystemManagers[0].addEventListener("callLaterError",
systemManager_callLaterError);
}
private function systemManager_callLaterError(event:DynamicEvent):void {
Alert.show(event.error.message + "\n" + event.error.getStackTrace());
}
On Tue, Nov 1, 2016 at 8:11 AM, mark goldin <[email protected]> wrote:
> We have flex 3 app compiled with 4.13 SDK. in our development environment
> everything works fine. But on the customer site some users are having
> problems running it in IE. The app starts loading showing a progress bar
> but then the whole screen becomes black. Any idea what that might be? Any
> debuging suggestions?
>
> Thanks
>