We just released Oracle Enterprise Pack for Eclipse (OEPE) 184.108.40.206.1 - 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
you have upgraded to OEPE 220.127.116.11.1 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 18.104.22.168.1.
To update you have to one of two options:
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).
MAF 22.214.171.124.1 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.
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)
Android SDK Tools 23
Version 23 of the
SDK tools will work with OEPE 126.96.36.199.1, 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
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
If this happens try the following:
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.
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.