Paul Johl | Consulting Product Manager
Oracle Mobile Application Framework (MAF) release, 2.5.1
This is a minor release containing a number of platform upgrades and enhancements, including the following:
- This release updates the Cordova engine versions that MAF uses (Android: 7.0.0 and iOS: 4.5.4).
- On iOS and Android platforms, applications can be suspended or terminated by the operating system if they are not foreground applications or when the device is locked. We have added APIs to wrap background tasks so the application is not suspended while the tasks are in operation. For more information, see Allowing Background Thread Processing on iOS and Android Devices.
- On the Android platform:
- You must install Android API Level 27 as described in Setting Up Development Tools for the Android Platform.
- You can specify the CPU type for deployment, see Deploying a MAF Application to the Android Platform.
- MAF now declares the default hostname verification process as
STRICT. You can override this, as described in How to Update Connection Attributes of a Named Connection at Runtime. - MAF now removes all session cookies when a user logs out of a MAF application. You can override this, as described in How to Update Connection Attributes of a Named Connection at Runtime.
- MAF now provides a new core plugin, Google Geolocation Play Services, as described in Introduction to Using Plugins in MAF Applications.
- On the Universal Windows Platform, the MAF for Windows deployment profile can now invoke a Select Custom Color dialog for the splash screen. See Deploying a MAF Application to the Universal Windows Platform.
- Starting with this release, you can specify the languages supported by your MAF application. Only the supported languages you specify for the application are reported on the application stores and upload consoles. For more information, see Specifying Supported Languages for Your Application.
- This release removes the
amx:inputDatecomponent. We recommend that customers use theinput type="date"element. - MAF now uses a thread pool to manage processing whereas previously it used one static thread per application feature. This change optimizes memory usage by MAF applications.
Please refer to the What's New section of the developer guide for detailed information about the changes and how they may affect you.
For additional release information, such as release notes and certification matrix, please refer to the MAF documentation on OTN.
We always encourage you to upgrade to this latest MAF release as soon as possible!
Paul Johl | Consulting Product Manager
