Oracle Enterprise Pack for Eclipse - Updated Android SDK 23 Support for Oracle MAF

We just released Oracle Enterprise Pack for Eclipse (OEPE) - a minor release which resolves deployment issues discovered between the Android SDK tools 23 and Oracle Mobile Application Framework (Oracle MAF).

Try out this new release if you have been experiencing deployment issues on the new Android SDK.

Here is some additional info that you can also find in the what's new doc

Applying fix for SDK Tools 23 problems

If you have upgraded to OEPE in order to fix problems (zipalign is missing error) with your OEPE MAF build on Android SDK Tools 23, make sure that you update your deploy targets. OEPE deploy targets do not automatically update with
To update you have to one of two options:

  1. Delete and recreate your MAF 2.0 runtime targets for Android. You can do this by going to Project Properties->Mobile Application Framework on your assembly project and use the Remove and Add buttons to make the change.
  2. You can also manually apply the fix by deleting each "build-android.xml" for each target and then right-clicking on your assembly project and invoking Configure->Configure MAF application and then hitting Ok in the dialog without making any other change. This will replace the deleted build-android.xml file with one generated from the newest template. To find the "build-android.xml" file, disable filtering for files starting with "." in your package or common explorer. The targets for android have names like "" or "". Within that directory the build-android.xml is under the "bin" folder.

Android SDK API 4.4x (API 20)

The supported versions of the Android runtime API for MAF 2.0 are API versions 4.0.3 (API 15) through 4.4.2 (API 19).

OEPE MAF is not compatible with any version of the Android API later than 4.2.2 (API 19). The tooling will stop the user from using these later versions and MAF applications may even successfully deploy based on this version, however, they may fail at runtime.

If you have API 20 installed in the SDK you have registered with OEPE, be aware that OEPE will automatically pick this version (even though it is not supported) when you created new deployment targets. This is because the current default is to select the latest version. To workaround, simply remove the API 20 targets and create new API 19 (or earlier) targets.

Android SDK Tools 23

Version 23 of the SDK tools will work with OEPE, however the "Android SDK Build Tools" component must be upgraded to at least 19.1, otherwise there will be a failure an MAF application build time. This is due to version enforcement in the Android SDK itself (getbuildtools task) and cannot be otherwise worked around.

Google Cloud Messaging and Android SDK Tools 23

In some upgrade scenarios (principally after upgrading from Android SDK Tools 22.x to 23), the option to install the "Google Cloud Messaging for Android Library" disappears from SDK Manager. This component must be installed in your SDK for correct build and operation of MAF applications.

If this happens try the following:

  1. Ensure that the "Obsolete" flag is checked in SDK Manager.
  2. Restart SDK Manager. Then select Packages->Reload from the menu. This usually fixes the issue.
  3. If neither of the above fixes the issue you can follow these instructions for manual install:


Problem: Application deployment fails with the following error: The SDK Build Tools revision (19.0.3) is too low for project 'oepe-android-build'. Minimum required is 19.1.0
Solution: Open SDK Manager and upgrade your SDK Build Tools component to at least 19.1.0.

Problem: Deployment succeeds on my Android device or emulator, but the application hangs on the starting splash screen.
Solution: Check if the version of the platform API you used is newer than Android 4.2.2 (Platform 19). This will appear in the dialog when you right-click on the assembly project and select Properties->Mobile Application Framework under "Platform Version". If the value is greater than 19, then Remove the target and click Add.. to create one using a supported version. If a supported version does not appear, open SDK Manager and install one first.

Note: This problem may be caused by other issues. If this doesn't solve your problem, capture the logcat output for your application and post the information to MAF support forums for help.

Problem: Application deployment fails with the following error: .../sdk/extras/google/gcm/gcm-client/dist does not exist

Solution: Install the Google Cloud Message component from SDK Manager.


I am a bit confused on the supported versions, 4.2.2 is api 17.

Posted by guest on August 06, 2014 at 03:06 PM PDT #

I have the " .../sdk/extras/google/gcm/gcm-client/dist does not exist" error. I use OEPE and Android SDK 23.0.5 but I can not find Google Cloud Message in SDK Manager. Is there another solution?
I would like to use OEPE but I have a 32Bit System - could only find the 64Bit version of OEPE

Posted by guest on October 15, 2014 at 04:18 AM PDT #

To get the Google Cloud Message to show in the SDK manager check the "obsolete" check box and check under extras:

Posted by Shay on October 15, 2014 at 08:30 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

This blog is is dedicated to announcements,tips and tricks and other items related to developing, integrating, securing, and managing mobile applications using Oracle's Mobile Platform. It is created and maintained by the Oracle Mobile product development team.

Archive of past entries

Even More Mobile Development Blogs

Oracle A-Team Site - Mobile Related Entries

Code samples from the Community

Fusion Middleware Blogs


« July 2016