Skip to main content
Participant
April 5, 2013
Question

Nostalgic about 'apk-debug'

  • April 5, 2013
  • 5 replies
  • 2055 views

Although it was probably a wise move to remove support for shared runtime deployment in the 3.7 SDK it would still be handy to have the old 'apk-debug' mode around for testing purposes.

Building an app with the captive runtime increases both build and install times quite substantially so if there's any chance to bring back some sort of lightweight test mode that would be great.

This topic has been closed for replies.

5 replies

Participating Frequently
April 5, 2013

Hi,

Could you please let us know if there are any problems that you are facing with apk-debug target?

Participant
April 5, 2013

Sure, when I use ADT with "-target apk-debug" I get the following message:

NOTE: The AIR SDK no longer supports packaging android applications for use with the shared Runtime.

The application has been packaged with a captive Runtime.

So from what I can tell building with apk-debug is no different from building with apk-captive-runtime. Another thing I just noticed in 3.7 is that a file named adobeair.vch is now added to the build. Is this required and what does it do?

Thanks,

Lars

Participating Frequently
April 5, 2013

Yes, with AIR 3.7 all the Android applications will be captive. So, application packaged with apk-debug target will also have runtime embedded.

Please let us know if you are facing any issues with the application packaged with apk-debug target?

Also let us know the location of the file adobeair.vch file that you can see added to the build?

Thanks,

Krati