So are all Android apk's forced too captive runtime now?

Question

I published my Flex app (with a linked native extension) and it was 1.5Mb. But then I upgraded my AIRSDK to 3.7 and now it's 11.7Mb?

Whoa, that's huge!

Thinking this was a Flex problem I built a simple tester AS3 app in Flash Pro, linked in my ane and tried to publish. It went away for a long time then came back with a dialog:

"The APK was packaged successfully, but a warning occurred.

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 what gives?

And the apk was 9.3Mb.

Can I ask when this started so I know how far I need to fall back? AIR 3.5? (I know 3.4 was ok.)

Is this a permanent thing? Was it really necessary to force all mobile apps to giant captive runtimes?

Colin Holgate · Answer

It's a change with AIR 3.7. Not sure of all the reasons, but one of them might be to enable debugging with captive runtime. Previously you could not debug that way, and so you would have to either install the beta APK, or wait until the app stores had the AIR runtime to download. You could switch to AIR 3.6, so long as you're not interested in Kindle Fire (that's not compatible with the AIR 3.6 runtime, you have to use captive runtime for that).

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.