IBM Support

PI37961: APPLICATION CENTER CANNOT READ CERTAIN APK FILES IF THE AAPT TOOL IS NOT AVAILABLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When uploading certain Android APK files to the Application
    Center, if neither of the the propertes "android.aapt" or
    "android.aapt.dir" are set and point to a usable version of the
    AAPT tool, then the upload may fail, and an error may appear in
    the server log that looks similar to:
    
    [3/26/15 13:32:24:376 EDT] 00000024
    com.ibm.puremeap.services.UploadService                      E
    Exception during resource upload. null
    [3/26/15 13:32:24:383 EDT] 00000024
    com.ibm.puremeap.services.UploadService                      E {
     "id": "919c6cf4-5a70-47b0-9456-18ca0c50a847",
     "message": "FWLAC0000E: A server error was detected.",
     "productVersion": "6.1.0"
    }
    java.lang.NullPointerException
     at java.util.HashMap.putAll(HashMap.java:739)
    

Local fix

  • As a workaround, one of the properties "android.aapt" or
    "android.aapt.dir" may be set pointing to a usable version of
    the AAP tool.  This workaround is not available on AIX systems.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Application Center that upload an Android APK file  *
    * when the Application Center Server is installed on a         *
    * platform where the aapt tool is not available.               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The Application Center has two ways to parse an Android APK  *
    * file: by using the aapt tool from the Android SDK, or by a   *
    * fallback routine if the aapt tool is not available. The      *
    * fallback routine contains a programming error that fails to  *
    * read the text chunk section of the Android Manifest in the   *
    * APK file. This causes the upload of some APK files to fail,  *
    * and the user sees an upload error message in the Application *
    * Center Console.                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * -                                                            *
    ****************************************************************
    

Problem conclusion

  • The fallback routine has been modified to read the text chunk
    section of the Android Manifest in the APK file correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI37961

  • Reported component name

    WL/MFPF CONSUME

  • Reported component ID

    5725I4301

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-27

  • Closed date

    2015-04-29

  • Last modified date

    2015-04-29

  • 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

    WL/MFPF CONSUME

  • Fixed component ID

    5725I4301

Applicable component levels

  • R600 PSY

       UP

  • R610 PSY

       UP

  • R620 PSY

       UP

  • R630 PSY

       UP

  • R700 PSY

       UP

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

Document Information

Modified date:
17 October 2021