IBM Support

PI56336: "UNABLE TO EXECUTE DEX" ERROR EXCEEDING 65K METHODS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using Android's Eclipse ADT plugin has a limit of 65k methods.
    When a Mobile First Platform Foundation (MFPF) Studio Android
    application adds a large library such as Google Play Services,
    the dex limit is exceeded and unable to run the app. The
    recommended solution is to migrate the Eclipse based project to
    an Android Studio Gradle based project and use Gradle to enable
    multiDex. However, conversion of an MFPF Studio Project to
    Android Studio project causes some problems with the Android
    Studio project, so migration was never recommended and was not
    supported in the past. In order to fix this dex issue, support
    for migration to Android Studio will be added and the MFPF
    Studio project will no longer interfere with the Android Studio
    project.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who get a Dex error for exceeding 65,000 methods in    *
    * MobileFirst Platform Foundation Android applications.        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MobileFirst Platform Foundation Android applications made in *
    * Eclipse have a dex limit of 65,000 methods. Importing large  *
    * libraries such as Google Play Services may push some         *
    * applications over the limit of 65,000 methods and will       *
    * prevent the application from building. The solution is to    *
    * migrate the application to Android Studio and build with     *
    * Gradle instead of Ant, which has settings that allows for    *
    * multi-dex support. For MobileFirst to support Android        *
    * Studio, some build changes needed to be made in the          *
    * MobileFirst application build process to not overwrite       *
    * Android Studio files. After those changes have been applied, *
    * users should be able to migrate their application to Android *
    * Studio, make changes in Eclipse, build and deploy to server  *
    * in Eclipse, and then deploy and run their application in     *
    * Android Studio.                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * -                                                            *
    ****************************************************************
    

Problem conclusion

  • After installing the iFix, rebuild the application.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI56336

  • Reported component name

    MFPF/WORKLIGHT

  • Reported component ID

    5725I4301

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-29

  • Closed date

    2016-03-18

  • Last modified date

    2016-03-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MFPF/WORKLIGHT

  • Fixed component ID

    5725I4301

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZH4A","label":"IBM Worklight"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021