Skip Headers
Oracle® Fusion Middleware Mobile Developer's Guide for Oracle Application Development Framework
11g Release 2 (11.1.2.4.0)

Part Number E24475-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Troubleshooting

This appendix describes problems with various aspects of ADF Mobile applications, as well as how to diagnose and resolve them.

This appendix includes the following sections:

A.1 Problems with Input Components on iOS Simulators

Issue:

On ADF Mobile applications deployed to iOS simulators, text entered into one <amx:inputText> component field becomes attached to the beginning of the text entered in subsequent field when navigating from one field to another using a mouse. For example, on a page with First Name, Middle Name, and Last Name input text fields, if you enter John in the First Name field, then click the Middle Name field, and enter P, the text displays as JohnP. Likewise, when you click the Last Name field, and enter Smith, the text in that field displays as JohnPSmith, as shown in Figure A-1.

Figure A-1 Text Values Concatenate in Subsequent <amx:inputText> fields

Text problems on iOS simulator.

Note:

This behavior only occurs on iOS simulators and in web pages, not on actual devices.

Solution:

Use the keyboard on the simulator to traverse the input text fields rather than the mouse.

A.2 Code Signing Issues Prevent Deployment

Issue:

In some iOS development environments, ADF Mobile application deployment fails because of code signing errors.

Solution:

To ensure that the ADF Mobile application is signed, add code signing data to the Mach-O (Mach object) file by configuring the environment with CODESIGN_ALLOCATE. For example, enter the following from the Terminal:

export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate"

For more information, see codesign_allocate(1) OS X Manual Page and OS X ABI Mach-O File Format Reference, both available from the iOS Developer Library (http://developer.apple.com/library/ios/navigation/).

A.3 Missing Android SDK Tools File Prevents Deployment

Issue:

Deployment of an Android application fails because ADF Mobile cannot locate the aapt file. ADF Mobile writes an error similar to the following in the Deployment-Log window:

[07:54:28 PM] Shutting down Android Debug Bridge server...
[07:54:28 PM] Deployment cancelled.
[07:54:28 PM] ---- Deployment incomplete ----.
[07:54:28 PM] Cannot run program ""C:\Program Files(x86)\AndroidSDK\sdk\platform-tools\aapt"":
              CreateProcess error=2, The system cannot find the file specified
[07:54:28 PM] CreateProcess error=2, The system cannot find the file specified

Solution:

Verify that the location defined in the Android Build Tools Location field of the ADF Mobile Platforms page references the directory that contains the aapt file (aapt.exe on Windows systems). For Revision 22 of the Android SDK, this file, along with all of the other build tools components, is located within the build-tools directory. For earlier revisions, the build tools components are located in the platform-tools directory. For more information, see Section 17.2.3, "How to Create an Android Deployment Profile." See also Exploring the SDK, available from the Android Developers website (http://developer.android.com/sdk/exploring.html).