Adl Error Application Descriptor Not Found
Using ADL, you can run an application without first packaging and installing it. By default, ADL uses a runtime included with the SDK, which means you do not
Adl Initial Content Not Found
have to install the runtime separately to use ADL. ADL prints trace statements air debug launcher and run-time errors to the standard output, but does not support breakpoints or other debugging features. You can use
Error While Loading Initial Content
the Flash Debugger (or an integrated development environment such as Flash Builder) for complex debugging issues. Note: If your trace() statements do not display on the console, ensure that you have not specified adobe air debug ErrorReportingEnable or TraceOutputFileEnable in the mm.cfg file. For more information on the platform-specific location of this file, see Editing the mm.cfg file. AIR supports debugging directly, so you do not need a debug version of the runtime (as you would with Adobe® Flash® Player). To conduct command-line debugging, you use the Flash Debugger and the AIR Debug Launcher (ADL). The Flash Debugger is distributed in the adobe air adt Flex SDK directory. The native versions, such as fdb.exe on Windows, are in the bin subdirectory. The Java version is in the lib subdirectory. The AIR Debug Launcher, adl.exe, is in the bin directory of your Flex SDK installation. (There is no separate Java version). Note: You cannot start an AIR application directly with fdb, because fdb attempts to launch it with Flash Player. Instead, let the AIR application connect to a running fdb session. ADL usageTo run an application with ADL, use the following pattern: adl application.xml Where application.xml is the application descriptor file for the application. The full syntax for the ADL is: adl [-runtime runtime-directory] [-pubid publisher-id] [-nodebug] [-atlogin] [-profile profileName] [-screensize value] [-extdir extension-directory] application.xml [root-directory] [-- arguments] (Items in brackets, , are optional.) -runtime runtime-directory Specifies the directory containing the runtime to use. If not specified, the runtime directory in the same SDK as the ADL program is used. If you move ADL out of its SDK folder, specify the runtime directory. On Windows and Linux, specify the directory containing the Adobe AIR directory. On Mac OS X, specify the directory containing Adobe AIR.framework. -pubid publisher-id Assigns the specified v
Votes: 0 Watchers: 2 Operations If you were logged in you would be able to see more operations. FDT I can
Application Descriptor Not Found Adobe Air
not resolve an error "application descriptor not found" when I try air sdk to launch a mobile application on the desktop Created: 06/Nov/11 12:54 PM Updated: 22/Jun/12 07:01 PM Component/s: AIR Affects Version/s: FDT 5.5.2 Fix Version/s: FDT 5.5 Security Level: public Time Tracking: Not Specified Environment: « Hide Windows 7 Home Premium 64bits FDT 18.104.22.1683 http://help.adobe.com/en_US/air/build/WSfffb011ac560372f-6fa6d7e0128cca93d31-8000.html Flex SDK 22.214.171.12428 AIR SDK 3.0 Show » Windows 7 Home Premium 64bits FDT 126.96.36.1993 Flex SDK 188.8.131.5228 AIR SDK 3.0 Review Type: Review by Developer Description « Hide This bug is still persistent in FDT 184.108.40.2063.. Just create empty hello world project (type AIR for Desktop) and still getting "application descriptor not found" message! I checked the http://bugs.powerflasher.com/jira/browse/FDT-2407 .settings>launch file and the key is there :
times are UTC Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group. Designed by ST Software for PTF.
Trying to launch my AIR project on the emulator, I keep getting D:\flex_sdk_4.6_Air_3.8\bin\adl.exe -profile extendedMobileDevice -screensize iPhoneRetina -XscreenDPI 326 -XversionPlatform IOS -XscreenDPI326 -extdir C:\Users\xxx\AppData\Local\Temp\IntelliJ_ANE_unzipped D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug-emulator\DevEmuHeadrApplication-app.xml D:\Headr\trunk\headr-app\headr-mobile\app\bin-debug-emulator[AIR Debug Launcher]: application descriptor not found[AIR Debug Launcher]: Process finished with exit code 6I can launch it fine on the device via USB.Any ideas how I can debug this further?I'm not sure how/if it relates to IntelliJ eitherThis broke somewhere along the way when I upgraded to 12.1.4. Perhaps I lost some settings somehow ?:|Thanks! Facebook Twitter LinkedIn Google+ Date Votes 2 comments 0 Alexander Doroshko September 12, 2013 19:53 Do you have any custom ADL option set in the run configuration (Run | Edit configurations...)? I see a strange and incorrect command line option '-XscreenDPI326' that breaks the command line syntax. Is it your mistake?By the way you don't need to specify screen resolution manually as additional ADL option as it is done automatically. 0 Melissa Y September 13, 2013 09:43 Thanks!!! that was my mistake. emulator is back up and running. happy dance Please sign in to leave a comment.