Highlighted

Adobe AIR SDK 4 - no 'bundle' target?

New Here ,
Mar 19, 2014

Copy link to clipboard

Copied

Hi,

I have been building a native AIR desktop installer using -target native. However, I want to include a captive runtime as the user may not have the AIR runtime nor an internet connection.

The docs suggest that -target bundle is my friend, and then I can build my own installer from the folder it builds.  However, my version of adt (I have v4.0 of the SDK) seems not to have this target!

> adt -package -storetype pkcs12 -keystore selfcert.p12 -storepass ****** -target bundle ******* config.xml index.html css fonts img js thankyou.png

Unknown package target bundle

usage:

  adt -checkstore SIGNING_OPTIONS

  adt -certificate -cn <name> ( -ou <org-unit> )? ( -o <org-name> )? ( -c <country> )? ( -validityPeriod <years> )? ( 10

24-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 ) ( CONNECT_OPTIONS? | -listen <port>? ) ( -airDownloadURL <url>

)? SIGNING_OPTIONS <output-package> ( <app-desc> PLATFORM-SDK-OPTION? FILE-OPTIONS | <input-package> PLATFORM-SDK-OPTIO

N? )

  adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc ) CONNECT_OPTIONS? SIGNING_OPTIONS <output-pa

ckage> ( FILE_OPTIONS | <input-package> )

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

age> )

  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 -installRuntime   PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? ( -package <apk-file> )?

  adt -installApp       PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? -package <apk-file>

  adt -uninstallRuntime PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )?

  adt -uninstallApp     PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? -appid <app-id>

  adt -launchApp        { PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? ( -debuggerPort port )? -appid <a

pp-id> }

  adt -runtimeVersion   PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )?

  adt -appVersion       PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? -appid <app-id>

  adt -version

TOPICS
Development

Views

559

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Adobe AIR SDK 4 - no 'bundle' target?

New Here ,
Mar 19, 2014

Copy link to clipboard

Copied

Hi,

I have been building a native AIR desktop installer using -target native. However, I want to include a captive runtime as the user may not have the AIR runtime nor an internet connection.

The docs suggest that -target bundle is my friend, and then I can build my own installer from the folder it builds.  However, my version of adt (I have v4.0 of the SDK) seems not to have this target!

> adt -package -storetype pkcs12 -keystore selfcert.p12 -storepass ****** -target bundle ******* config.xml index.html css fonts img js thankyou.png

Unknown package target bundle

usage:

  adt -checkstore SIGNING_OPTIONS

  adt -certificate -cn <name> ( -ou <org-unit> )? ( -o <org-name> )? ( -c <country> )? ( -validityPeriod <years> )? ( 10

24-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 ) ( CONNECT_OPTIONS? | -listen <port>? ) ( -airDownloadURL <url>

)? SIGNING_OPTIONS <output-package> ( <app-desc> PLATFORM-SDK-OPTION? FILE-OPTIONS | <input-package> PLATFORM-SDK-OPTIO

N? )

  adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc ) CONNECT_OPTIONS? SIGNING_OPTIONS <output-pa

ckage> ( FILE_OPTIONS | <input-package> )

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

age> )

  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 -installRuntime   PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? ( -package <apk-file> )?

  adt -installApp       PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? -package <apk-file>

  adt -uninstallRuntime PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )?

  adt -uninstallApp     PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? -appid <app-id>

  adt -launchApp        { PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? ( -debuggerPort port )? -appid <a

pp-id> }

  adt -runtimeVersion   PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )?

  adt -appVersion       PLATFORM-OPTION PLATFORM-SDK-OPTION? ( -device <deviceID> )? -appid <app-id>

  adt -version

TOPICS
Development

Views

560

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Mar 19, 2014 0
Adobe Community Professional ,
Mar 19, 2014

Copy link to clipboard

Copied

The last few releases of AIR require that it be captive runtime. That’s why there isn’t that option anymore. The APKs you’re getting are already captive runtime.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 19, 2014 0
New Here ,
Mar 19, 2014

Copy link to clipboard

Copied

Hi Colin. Thanks for your reply. I don't believe they are already captive runtime, because:

  1. when I run them on an Internet-connected computer the installer shows the 'Also download the AIR runtime' option ticked and greyed out, and
  2. when I run them on a laptop with no net connection, I get an error message saying the AIR runtime is required/not present

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 19, 2014 0
Adobe Community Professional ,
Mar 19, 2014

Copy link to clipboard

Copied

Sorry, thought you were talking about mobile Android, not desktop.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 19, 2014 0
PaulMG LATEST
New Here ,
Mar 19, 2014

Copy link to clipboard

Copied

Oh yeah -- I didn't see the word 'APK' or I would have realised your mistake.

No, I'm talking about a desktop installer for Windows EXE

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 19, 2014 0