Could you try enabling automatic dump file creation and try launching your app again to see if it's actually crashing? If it is, please send me the dmp file (email@example.com). I'd also be happy to try this myself if you'd like to just send me the .air file instead.
See this post for .reg files to enable/disable dump file creation.
Thanks a lot for your reponse. I tried the thing you suggested, but strangely no folder by that name (in the other thread you linked) existed, before or after the app crashed. I tried a few other things, like running the AIR app through the ADL, to see if that would produce the error log you were describing.
I got an error when using the ADL, 'initial content not found'. I thought maybe some of the assets weren't being loaded correctly, so I went through and put in loads of logging, using the SOS Max Logger. Whilst doing this, I decided to remove a trace() statement I had, or rather change it so it used the logger. This is what I changed:
trace("Load Progress: " + event.target.progress);
logger.debug("Load Progress: " + event.target.progress);
The event is a LoaderEvent, from the LoaderMax lib. After this change, the app worked after installation. I had to then back-track through all my changes to see what caused it, and found that this was it.
I'm a bit dumbfounded as to why this caused the problem. I still have other trace() statements in there, that cause no problems at all. Seemingly it's having the event.target.progress thing in there that makes the difference.
Anyway, thanks for your help Chris.
Hi Chris and Jonnex
Did you find out the solution?
Even i'm getting the same issue. Except that i'm not getting any errors.
When i first run my application it showed me the GUI for half second and closed. Then i tried to reopen the app its not at all showing any window.
I does not show any errors.
I even tried enabling Crash Logging, but havent found any folder named CrashDump in my Windows folder.
If you guys found any solution please update to the forum..
Unfortunately I can't offer you much more insight than the information I wrote in my last post. The only thing I was able to track this back to (my own problem) was using a trace statement. I checked several times to assure myself that this was the problem, and found it to be 100% related to using a trace at somepoint during the application's loading.
I can only suggest you try to remove all your trace statements; if the problem is the same one I had, this will hopefully fix your problem. If not, continue with the possible solution offered by Chris, and send him your logs.
Sure i have sent it via yousendit.com so please you this link
Link Expires on Jun 14 2012.
Since the app is using native process so i have to create exe instead of air
I just did the same thing.
The build was crashing. I traced the bug to a trace() command.
However, mine did not have any progress event attached to it.
if (level == LogLevel.ERROR)
trace("*** Error:" + msg + " ***");
else if (debugMode)
trace("message: " + msg);
When I commented out the two trace() commands above, the app compiled.