There are four combinations to try: 1) debug build in debugger player, 2) release build in debugger player, 3) debug build in release player and 4) release build in release player.
You've told us #1 works. If #2 fails, trace statements will help. If your only failure cases are #3 or #4, you'll have to instrument your code to try to find the issue. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of jimmy5804 Sent: Friday, May 01, 2009 8:43 AM To: [email protected] Subject: [flexcoders] Re: Runs in debug mode, but not release build It's a big project. Most of the skins are programmatic, but I've verified all the support graphics for the main project are there. Guess I need to go through and check libraries. I don't have a lot of information as to the cause right now. The logs that I have appear normal but nothing shows up when it is executed although the process continues to run. It may well be a graphic from a support library. As far as trace, how do you use that in an export release? I created a file logger for our logging infrastructure and I'll see what I can come up with. --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, "Tracy Spratt" <tr...@...> wrote: > > Are there any support folders or files missing from the export build? > > > > "long binary search". trace() might be easier and could give you more > information. > > > > More information here might help also. > > > > Tracy Spratt, > > Lariat Services, development services available > > _____ > > From: [email protected]<mailto:flexcoders%40yahoogroups.com> > [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On > Behalf Of jimmy5804 > Sent: Friday, May 01, 2009 1:47 AM > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Runs in debug mode, but not release build > > > > > > > > > > AIR app. Runs fine in debug, but fails to initialize when build is exported. > After a long binary search I found it fails silently on addition of a > particular (important) child. Anyone seen anything like this before? >
