Android 4.3 has broken AIR 3.7 apps

[banzai76_]

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

[nimitja]

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

[OMA2k]

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!

[nimitja]

Please compiled and run your application with AIR SDK 3.7 build 3.7.0.210 or AIR SDK 3.8 available at :http://helpx.adobe.com/air/kb/archived-air-sdk-version.html. Please let us know if you will face any problem.

Regards,

Nimit

[Push76]

Hi all

Please can you help?

I'm using Windows 7 and Adobe Flash CS6.

I have an app that I am trying to deploy to a Nexus 7 running Android 4.3.

I've tried publishing the application using the following versions of the AIR SDK.

• AIR 3.7.0.1530 for Android
• AIR 3.8.0.870 for Android
• AIR 3.4 for Android

All of these fail with numerous problems along the way.  Here are some of the issues:

(you would think this is a driver issue but all drivers are up to date).

Anyway, the apk file publishes ok so I manually drag it onto the device into the "Download" folder on the Nexus. Using Windows Explorer.

I get errors like this on the Nexus when trying to install:

...and I do have USB debugging checked:

If I browse to the .apk file and then change its file extension to be .zip and then unzip it I can explore and find AndroidManifest.xml.

When I view the AndroidManifest.xml file it is unreadable.  It looks like this:

This might be like this to stop people from reading it for security purposes.  I don't know though.

So - I'm stuck at the moment.

Does anybody have anything else I can try in order to get this working?

Thanks in advance

James

[banzai76_]

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

[Push76]

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

[Push76]

This is the Google USB Driver.

http://developer.android.com/sdk/win-usb.html#top

Installing this gives me SAMSUNG Android Phone > Android Composite ADB Interface in Device Manager.

Cheers banzai76_

[Push76]

I've got this working now.

In my case it was just down to the certificate.  I created a new one which fixed my issues.

(didn't fix the issue about Flash not being able to recognise that the Nexus was connected via USB though).  This I think is a driver issue.

(it would have been nice if Flash had thrown some sort of error about the certificate being invalid rather than building the apk with no errors).