Skip to main content
T
Tapockeck
Participating Frequently
May 19, 2017
Answered

Multidex for android api 20 and lower

  • May 19, 2017
  • 1 reply
  • 2577 views

Hello.
It looks like I found a problem with multidex in AIR SDK 25. It works properly with android API 21+. But sometimes I receive crash reports with "ClassNotFoundException" from devices with old android versions. After decompiling my application I found that some steps from android multidex enabling instruction are not performed:
Configure Apps with Over 64K Methods | Android Studio

Particularly, I found that my application tag (from AndroidManifest.xml) doesn't have android:name attribute. But the instruction clearly states that our minSDKVersion is set to 20 or lower, we need to use MultidesApplication as follows:
<application
            android:name="android.support.multidex.MultiDexApplication" >
        ...
</application>

Or our Application class should extend MultiDexApplication class (and our application class should be in android:name attribute).

So, it looks like defects on your side influence my application. How can I fix it?

This topic has been closed for replies.
Correct answer Rohit_Kumar2

Hey Tapockeck,

Yes, you can provide the flag in the descriptor file for all the applications.

By default, we have enabled multidex for all the apps but it should come in action in the cases when 64K references limit exceeds.

Please let us know if providing the tag solves your problem. We have logged a bug for this. In the next release, we will try to include it by default to avoid any confusion.

Thanks,

Rohit

Adobe AIR Team

1 reply

T
TapockeckAuthor
Participating Frequently
May 19, 2017

I think that I can add android:name in my descriptor file, but I don't know in what cases multidex will be enabled.

Rohit_Kumar2
Adobe Employee
Rohit_Kumar2Correct answer
Adobe Employee
May 24, 2017

Hey Tapockeck,

Yes, you can provide the flag in the descriptor file for all the applications.

By default, we have enabled multidex for all the apps but it should come in action in the cases when 64K references limit exceeds.

Please let us know if providing the tag solves your problem. We have logged a bug for this. In the next release, we will try to include it by default to avoid any confusion.

Thanks,

Rohit

Adobe AIR Team

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