This content has been marked as final. Show 3 replies
You could write to a file. Replace all your air.trace calls with a custom function that calls air.trace then calls another function that opens a log file you create, writes to it.
What about *errors*? If my installed app has a .js error, where can I see it?
You can enable logging to a text file using settings in the mm.cfg file. See http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19323
Note that ALL trace output will go to the log.
Other things you can do are:
1. Run the installed app with adl -- just pass the installed app descriptor to adl on the command line
2. Supply a publisher id to adl. This removes one difference between installed/ not installed apps and may be enough if the behavior issue has to do with local connections or other matters involving the publisher id.
3. Use the adl -nodebug flag. This removes another difference between installed/uninstalled apps. You won't see uncaught exceptions, but trace statements are still reported.