Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of marrtinmiko@gmail.com
 designates 209.85.217.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACNHA5Dp+KpYmouVcSn0bF2w=eZLennsSv-x+OGTQ6=JjvwGcw@mail.gmail.com>
References: 
 <41297e1c9e5f67e25bf611bfa2d02959@webmail.informatik.uni-bremen.de>
	<AF4B54DB-E86E-4B17-8E41-0491DC128578@att.net>
	<CACNHA5Dp+KpYmouVcSn0bF2w=eZLennsSv-x+OGTQ6=JjvwGcw@mail.gmail.com>
Date: Wed, 24 Jul 2013 15:52:03 +0200
Message-ID: 
 <CADPpF_2a0FTKiuMMe=q_Kt+U66A59nCBh3=CtABnY9tDb-J6Lg@mail.gmail.com>
Subject: Re: Captive Runtime Export Debug?
From: Martin Miko <marrtinmiko@gmail.com>
To: users@flex.apache.org
Content-Type: multipart/alternative; boundary=089e0116014ee6143b04e2423665

--089e0116014ee6143b04e2423665
Content-Type: text/plain; charset=ISO-8859-1

Hello Jan,

first of all, given your description it is hard to say what can be causing
your problems, because it can be virtually anything. I've seen similar "odd
behaviour" couple of times, the most common are timing issue that do not
manifest in the debug/profile regime due to some extra stuff that happens
when you run the app this way, followed by "something gets misconfigured or
not included" during the release.

Except the methods Stephen and Gerald mentioned there are quite a few
possibilities here. Since you're using AIR as I got it from your email, you
can set up very simple logger that will log into a file. Another "creative"
option is to swap the optimized swf that the release build outputs. What
you want to do is to replace the app swf in your app's installation folder
with the debug one from project's bin debug folder, run it via adl [1] and
connect with a command line debugger fdb [2][3]. The latter one is a bit
tedious and even might not help in case of timing issues, but on the other
hand it can help in many situations when logging isn't enough.
Alternatively you can use other debug tools for flash/air, unluckily I have
no experience with stuff like monster debugger [4], but I bet google will
gladly help in this case. ;)

[1]
http://livedocs.adobe.com/flex/3/html/help.html?content=CommandLineTools_4.html
[2]
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7ffb.html

[3]
http://livedocs.adobe.com/flex/3/html/help.html?content=debugging_03.html
[4] http://demonsterdebugger.com/tour


On Wed, Jul 24, 2013 at 2:53 PM, Stephen C <stephen@stephenjc.com> wrote:

> I wrap trace in a function that also put the info in a sharedobject. I
> have a log viewer in my app that shows past traces for debug in
> production.
> Thank You,
> Stephen C
> -All of my email addresses go to the same place
> -Save Paper, think before you print
> -PGP Public Key
>
>
> On Wed, Jul 24, 2013 at 8:50 AM, Gerald Chastain <woodychastain@att.net>
> wrote:
> > If you just have a few places to check try the old-fashioned way: use
> Alerts.
> >
> > Good luck,
> > Woody
> >
> > On Jul 24, 2013, at 5:03 AM, jank87 <jank87@informatik.uni-bremen.de>
> wrote:
> >
> >> Hi there,
> >>
> >> got an issue with the release export (captive runtime package) and
> can't figure out why it fails at a certain point. In Flash Builder
> Normal/Debug Mode everything works fine. My application uses a lot of blind
> approaches with try-catch conditions. May it be the Error throwing causing
> a fail? How can I "trace" errors in my export bundle.
> >>
> >> Best,
> >> Jan
> >
>


-- 
Martin Miko

--089e0116014ee6143b04e2423665--