ADT Command Not Working

Report · Apr 24, 2014

I'm trying to package up a Mac OS X Native application with the following command:

`adt –package -storetype pkcs12 -keystore HelloWorld.p12 HelloWorld.xml`

However I get the error:

`unexpected argument –package`

What am I doing wrong? I'm expecting to create `HelloWorld.app` from the command... Can anyone help?

Report · Apr 24, 2014

Looks like you need add ADT to environment variables.

http://help.adobe.com/en_US/air/build/WSfffb011ac560372f-71994050128cca87097-8000.html

Report · Apr 24, 2014

If I do this:

adt -version

I get:

13.0.0.83

So that should mean environment variables are set up fine right? ADL works fine too.

Report · Apr 25, 2014

Looks like you're using --package rather than using -package:

`adt –package -storetype pkcs12 -keystore HelloWorld.p12 HelloWorld.xml`

Report · Apr 25, 2014

That's fixed the first issue, but after been asked for the password for the certificate and entering it, I then get the error that there are not enough arguments?

This is the full code in the terminal:

Cameron:helloworld cameron$ adt -package -storetype pkcs12 -keystore HelloWorld.p12 HelloWorld.xml

password:

not enough arguments

usage:

adt -checkstore SIGNING_OPTIONS

adt -certificate -cn <name> ( -ou <org-unit> )? ( -o <org-name> )? ( -c <country> )? ( -validityPeriod <years> )? ( 1024-RSA | 2048-RSA ) <pfx-file> <password>

adt -help

adt -migrate SIGNING_OPTIONS ( <air-file-in> | <airn-file-in> ) <output-file>

adt -package SIGNING_OPTIONS ( -target air )? <output-package> ( <app-desc> FILE_OPTIONS | <input-package> )

adt -package SIGNING_OPTIONS -target airn <output-package> ( <app-desc> FILE-AND-PATH-OPTIONS | <input-package> )

adt -package -target ( apk | apk-debug | apk-emulator | apk-captive-runtime ) ( CONNECT_OPTIONS? | LISTEN_OPTIONS? ) ( -airDownloadURL <url> )? SIGNING_OPTIONS <output-package> ( <app-desc> PLATFORM-SDK-OPTION? FILE-AND-PATH-OPTIONS | <input-package> PLATFORM-SDK-OPTION? )

adt -package SIGNING_OPTIONS? -target native SIGNING_OPTIONS? <output-package> ( <app-desc> FILE-AND-PATH-OPTIONS | <input-package> )

adt -package SIGNING_OPTIONS? -migrate SIGNING_OPTIONS -target native SIGNING_OPTIONS? <output-package> <app-desc> FILE_OPTIONS PATH-OPTION

adt -package SIGNING_OPTIONS? -target bundle SIGNING_OPTIONS? <output-package> ( <app-desc> FILE-AND-PATH-OPTIONS | <input-package> )

adt -package SIGNING_OPTIONS? -target ane <output-package> <ext-desc> ANE_OPTIONS

adt -prepare <airi-file> <app-desc> FILE_AND_PATH_OPTIONS

adt -sign SIGNING_OPTIONS ( -target ( air | airn | ane ) )? ( <airi-file> | <unsigned-ane-file> ) <output-file>

adt -devices PLATFORM-OPTION PLATFORM-SDK-OPTION?

adt -installRuntime PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? ( -package <apk-file> )?

adt -installApp PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? -package <apk-file | ipa-file>

adt -uninstallRuntime PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION?

adt -uninstallApp PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? -appid <app-id>

adt -launchApp { PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION? ( -debuggerPort port )? -appid <app-id> }

adt -runtimeVersion PLATFORM-OPTION PLATFORM-SDK-OPTION? DEVICE-OPTION?

Report · Nov 27, 2018

As Nimisha1 mentioned, I believe the `unexpected argument –package` message is due to the dash not being correct.

I've just had the same issue from copying and pasting.

Delete the dash and type a minus ( - ) character.