IBM Support

PM79139: APPLICATIONS RUNNING ON ANDROID 4.2 FAIL TO LAUNCH PROPERLY WHEN SETTING MINSDKVERSION="17" IN ANDROIDMANIFEST.XML

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When setting minSdkVersion="17" in the AndroidManifest.xml file
    and running on Android 4.2, errors similar to the following may
    be seen in Android LogCat:
    processMessage failed: Stack: TypeError: Object [object Object]
    has no method 'init'
    11-27 12:04:35.806: D/CordovaLog(8963):     at [object
    Object].init
    (file:///data/data/com.bbb/files/www/default/wlclient/js/wlgap.a
    ndroid.js:576:27)
    11-27 12:04:35.806: D/CordovaLog(8963):     at onEnvInit
    (file:///data/data/com.bbb/files/www/default/wlclient/js/wlclien
    t.js:865:28)
    11-27 12:04:35.806: D/CordovaLog(8963):     at
    file:///data/data/com.bbb/files/www/default/wlclient/js/wlclient
    .js:1114:17
    

Local fix

  • As a workaround it is recommended for developers to set the
    minSdkVersion property to a value lower than "17".
    The defult minSdkVersion propery set by the Worklight android
    environment template is "8" (Android 2.2).
    If the developer has not installed the Android 2.2 API on his
    development environment, the Worklight template will pick the
    lowest API level installed which is larger than "8".
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Developers building applications for Android 4.2.            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Android 4.2 added restrictions for executing Java code from  *
    * JavaScript. In such a case, the Java API needs to be         *
    * annotated with @JavascriptInterface. The OS restriction is   *
    * applied when setting minSdkVersion to "17"  in the           *
    * AndroidManifest.XML file.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The code has been fixed so that applications running on Android
    4.2 will launch properly.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 5.0.6.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79139

  • Reported component name

    MOBILE FNDTN EN

  • Reported component ID

    5725G9200

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-13

  • Closed date

    2013-05-06

  • Last modified date

    2013-05-06

  • 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

    MOBILE FNDTN EN

  • Fixed component ID

    5725G9200

Applicable component levels

  • R500 PSY

       UP



Document information

More support for: IBM Mobile Foundation

Software version: 500

Reference #: PM79139

Modified date: 2013-05-06