IBM MobileFirst and Android Pie

Android Pie is here and IBM MobileFirst is ready for it.

In our previous blog post, we mentioned about the various new changes seen in Android Pie and what you, as a developer should be doing about it.

With the final release of Android Pie, we have validated MobileFirst v8.0 and v7.1 and the following features work fine with Android Pie.

  • Invoking backend procedures through adapters
  • Application Authenticity
  • Application management
  • Application Center
  • JSONStore
  • Direct Update
  • Oauth handshake with Mobile First server
  • Push notifications (v8)

Targeting your apps for API level 28

MobileFirst v8.0 apps

  • If you are targeting your MobileFirst v8 application for API level 28, you will have to update your Native Android project to point to the latest MobileFirst SDK If you are working on a Cordova project, please remove the cordova-plugin-mfp from your project and add the cordova-plugin-mfp@8.0.2018080605 version to your project.

    No action is required if the targetSdkVersion of your apps is 27 or lower. This is essential to accommodate the deprecated BC provider APIs in API 28.

  • If your app communicates over cleartext or HTTP, you will have to whitelist the domains to which cleartext traffic is allowed, in your apps Network security configuration. Read this article for more information

MobileFirst v7.1 apps

For MobileFirst v7.1 apps targeting API level 28, you will have to add the legacy Apache HTTP library as a dependency in your AndroidManifest.xml. Add the following line under the <application> tag of your AndroidManifest.xml.

<uses-library android:name="org.apache.http.legacy" android:required="false"/>
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.
Last modified on August 13, 2018