Highlighted

Android compilation splits into multiple dex files even though method limit is not hit

New Here ,
Feb 22, 2018

Copy link to clipboard

Copied

I'm trying to avoid having a multidex app, as it has a hit on app start time. I am pretty close to the border, but under it. However, I still get a classes.dex and classes2.dex files. When I analyse the resulting APK in android studio I see:

The total is 64295 references methods, under the 64k limit of 65536 references methods. Why is it creating 2 dex files and requiring me to add multidex support? Is there any way to solve this?

Using Adobe Air SDK 28

TOPICS
Performance issues

Views

189

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Android compilation splits into multiple dex files even though method limit is not hit

New Here ,
Feb 22, 2018

Copy link to clipboard

Copied

I'm trying to avoid having a multidex app, as it has a hit on app start time. I am pretty close to the border, but under it. However, I still get a classes.dex and classes2.dex files. When I analyse the resulting APK in android studio I see:

The total is 64295 references methods, under the 64k limit of 65536 references methods. Why is it creating 2 dex files and requiring me to add multidex support? Is there any way to solve this?

Using Adobe Air SDK 28

TOPICS
Performance issues

Views

190

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Feb 22, 2018 0

Have something to add?

Join the conversation