Skip to main content
B
banzai76_
Inspiring
August 1, 2013
Question

Android 4.3 has broken AIR 3.7 apps

  • August 1, 2013
  • 1 reply
  • 3158 views

Hi,

I just upgraded my Nexus 4 and Nexus 7 to Android 4.3. Some of my old air apps (installed before the update) won't run, some won't install when I download and run the apk, and some won't install from the adb command line. The errors are:

Downloading and running an apk: "Parse error: There was a problem while parsing the package."

Installing from adb command line:  "Failure[INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING]"

The common factor among the fails is that they were created with the AIR 3.7 sdk.

We can create and install new ones using AIR 3.8, but we're still faced with the propspect or rushing out updates before too many users have upgraded to Android 4.3.

Anybody else seeing this? I noticed one other post (http://forums.adobe.com/thread/1266823?tstart=0).

I guess not too many people have 4.3 yet.

Nick

    1 reply

    N
    Adobe Employee
    nimitja
    Adobe Employee
    August 2, 2013

    Hi,

    There was an issue(http://forums.adobe.com/message/5242715#5242715) presend in AIR 3.7.153 and later solved in 3.7.0.1760 due to which [INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING] error came. If you packaged your application with AIR SDK 3.7.0.1730 and later the issue  should not come. Also, are you able to install and debug your applications compiled and run with AIR SDK 3.8 on Android 4.3 devices.

    Regards,
    Nimit

    O
    OMA2k
    Inspiring
    August 2, 2013

    Hello nimitja. Thanks for your answer. Some of our users are having package signing problems in Android 4.3.

    Is there any way to tell what exact SDK version an APK was compiled with, including build number? (so we know updating the app in the Play Store with a recompiled version with a newer SDK will really solve the problem).

    Thanks!

    P
    Push76
    Participating Frequently
    August 13, 2013

    Your development setup is a bit different to mine, but I could suggest a couple of things:

    re: installing it directly onto the device. Do you have the Android SDK installed (with up to date Google USB drivers in the SDK manager)? And therefore when you look at Windows Device Manager with your Nexus plugged in, do you see 'Android Composite ADB Interface' in the list? I have found I need those drivers installed.

    re: the parse failed message. That's exactly what I saw, but only with AIR3.7. It's a hassle, but i'd suggest next trying it with AIR3.6? Just to get it up and running. http://helpx.adobe.com/air/kb/archived-air-sdk-version.html

    re: the AndroidManifest xml, it's stored in a binary XML format inside the apk, which is unreadable using a normal text editor. To recover it you would have to use something like 'apk tool', but I don't think that's related to your problem.

    Nick


    Thanks for your reply.  You're right about the manifest file and using the apk tool lets you read the file in all its glory.

    This is the tool:

    https://code.google.com/p/android-apktool/

    I'm going to re-visit the driver issue now.

    Cheers

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices