ADT error messages

The following tables list the possible errors that can be reported by the ADT program and the probable causes:

Application descriptor validation errors

Error code	Description	Notes
100	Application descriptor cannot be parsed	Check the application descriptor file for XML syntax errors such as unclosed tags.
101	Namespace is missing	Add the missing namespace.
102	Invalid namespace	Check the namespace spelling.
103	Unexpected element or attribute	Remove offending elements and attributes. Custom values are not allowed in the descriptor file. Check the spelling of element and attribute names. Make sure that elements are placed within the correct parent element and that attributes are used with the correct elements.
104	Missing element or attribute	Add the required element or attribute.
105	Element or attribute contains an invalid value	Correct the offending value.
106	Illegal window attribute combination	Some window settings, such as `transparency = true` and `systemChrome = standard` cannot be used together. Change one of the incompatible settings.
107	Window minimum size is larger than the window maximum size	Change either the minimum or the maximum size setting.
108	Attribute already used in prior element
109	Duplicate element.	Remove the duplicate element.
110	At least one element of the specified type is required.	Add the missing element.
111	None of the profiles listed in the application descriptor support native extensions.	Add a profile to the supportedProfies list that supports native extensions.
112	The AIR target doesn't support native extensions.	Choose a target that supports native extensions.
113	<nativeLibrary> and <initializer> must be provided together.	An initializer function must be specified for every native library in the native extension.
114	Found <finalizer> without <nativeLibrary>.	Do not specify a finalizer unless the platform uses a native library.
115	The default platform must not contain a native implementation.	Do not specify a native library in the default platform element.
116	Browser invocation is not supported for this target.	The `<allowBrowserInvocation>` element cannot be `true` for the specified packaging target.
117	This target requires at least namespace n to package native extensions.	Change the AIR namespace in the application descriptor to a supported value.

See AIR application descriptor files for information about the namespaces, elements, attributes, and their valid values.

Application icon errors

Error code

Description

Notes

200

Icon file cannot be opened

Check that the file exists at the specified path.

Use another application to ensure that the file can be opened.

201

Icon is the wrong size

Icon size (in pixels) must match the XML tag. For example, given the application descriptor element:

<image32x32>icon.png</image32x32>

The image in icon.png must be exactly 32x32 pixels.

202

Icon file contains an unsupported image format

Only the PNG format is supported. Convert images in other formats before packaging your application.

Application file errors

Error code	Description	Notes
300	Missing file, or file cannot be opened	A file specified on the command line cannot be found, or cannot be opened.
301	Application descriptor file missing or cannot be opened	The application descriptor file cannot be found at the specified path or cannot be opened.
302	Root content file missing from package	The SWF or HTML file referenced in the `<content>` element of the application descriptor must be added to the package by including it in the files listed on the ADT command line.
303	Icon file missing from package	The icon files specified in the application descriptor must be added to the package by including them among the files listed on the ADT command line. Icon files are not added automatically.
304	Initial window content is invalid	The file referenced in the `<content>` element of the application descriptor is not recognized as a valid HTML or SWF file.
305	Initial window content SWF version exceeds namespace version	The SWF version of the file referenced in the `<content>` element of the application descriptor is not supported by the version of AIR specified in the descriptor namespace. For example, attempting to package a SWF10 (Flash Player 10) file as the initial content of an AIR 1.1 application will generate this error.
306	Profile not supported.	The profile you are specifying in the application descriptor file is not supported. See supportedProfiles.
307	Namespace must be at least nnn.	Use the appropriate namespace for the features used in the application (such as the 2.0 namespace).

Exit codes for other errors

Exit code	Description	Notes
2	Usage error	Check the command-line arguments for errors
5	Unknown error	This error indicates a situation that cannot be explained by common error conditions. Possible root causes include incompatibility between ADT and the Java Runtime Environment, corrupt ADT or JRE installations, and programming errors within ADT.
6	Could not write to output directory	Make sure that the specified (or implied) output directory is accessible and that the containing drive is has sufficient disk space.
7	Could not access certificate	Make sure that the path to the keystore is specified correctly. Check that the certificate within the keystore can be accessed. The Java 1.6 Keytool utility can be used to help troubleshoot certificate access issues.
8	Invalid certificate	The certificate file is malformed, modified, expired, or revoked.
9	Could not sign AIR file	Verify the signing options passed to ADT.
10	Could not create time stamp	ADT could not establish a connection to the timestamp server. If you connect to the internet through a proxy server, you may need to configure the JRE proxy settings.
11	Certificate creation error	Verify the command-line arguments used for creating signatures.
12	Invalid input	Verify file paths and other arguments passed to ADT on the command line.
13	Missing device SDK	Verify the device SDK configuration. ADT cannot locate the device SDK required to execute the specified command.
14	Device error	ADT cannot execute the command because of a device restriction or problem. For example, this exit code is emitted when attempting to uninstall an app that is not actually installed.
15	No devices	Verify that a device is attached and turned on or that an emulator is running.
16	Missing GPL components	The current AIR SDK does not include all the components required to perform the request operation.
17	Device packaging tool failed.	The package could not be created because expected operating system components are missing.

Android errors

Exit code	Description	Notes
400	Current Android sdk version doesn't support attribute.	Check that the attribute name is spelled correctly and is a valid attribute for the element in which it appears. You may need to set the -platformsdk flag in the ADT command if the attribute was introduced after Android 2.2.
401	Current Android sdk version doesn't support attribute value	Check that the attribute value is spelled correctly and is a valid value for the attribute. You may need to set the -platformsdk flag in the ADT command if the attribute value was introduced after Android 2.2.
402	Current Android sdk version doesn't support XML tag	Check that the XML tag name is spelled correctly and is a valid Android manifest document element. You may need to set the -platformsdk flag in the ADT command if the element was introduced after Android 2.2.
403	Android tag is not allowed to be overridden	The application is attempting to override an Android manifest element that is reserved for use by AIR. See Android settings.
404	Android attribute is not allowed to be overridden	The application is attempting to override an Android manifest attribute that is reserved for use by AIR. See Android settings.
405	Android tag %1 must be the first element in manifestAdditions tag	Move the specified tag to the required location.
406	The attribute %1 of the android tag %2 has invalid value %3.	Supply a valid value for the attribute.