Preferences Dialog - Platforms Page

Tools Preferences ADF Mobile Platforms

Use this page to add the locations for the Android SDK and the iOS IDE. More

Supported Platforms
Select iOS or Android.

iOS Platform Options

iOS Simulator SDK Directory
Enter the location of the SDK for the iOS simulator, or select the location of the directory.

iOS xcodebuild Directory
Enter the location for the xcodebuild tool, or select the location of the directory.

"Automatically Add to iTunes" Directory
Enter the location of the Automatically Add to iTunes folder, or select the location of the directory.

Device Signing
You cannot publish an iOS application to either iTunes or to an internal distribution site without first obtaining a provisioning profile or a certification. You obtain these through the iOS Provisioning Portal. More

Provisioning Profile
Enter the location of the development or release version of the provisioning profile, which associates one or more development certificates and devices with an Application ID. You must obtain a provisioning profile from the iOS Provisioning Portal. You cannot publish an application to either iTunes or to an internal distribution site without first obtaining a provisioning profile. More

Certificate
Enter the signature that identifies the originator of the code (such as a developer or a company). The name, which is displayed in the Apple Keychain Access Utilitiy, must be in the following format:
iPhone Developer: John Smith (PN3ENLQ3DU). More

Android Platform Options

Android SDK Location
Enter the location of the Android SDK, or click Browse to select the location.

Android Platform Location
Enter the location of the Android platform, or click Browse to select the location.

Signing Credentials
Android applications must be signed before you deploy them to an Android device or emulator for testing, or to end users through an application marketplace, such as Google Play.

Debug
You can deploy an ADF Mobile application to an Android-powered device or Android emulator without having to provide a private key. Deployment will automatically create a debug key and keystore using the password entered in the Key and Keystore Password field.

Key and Keystore Password
Enter a password that deployment can use to create a debug key and keystore file. The password can have any value, but must be at least six characters long.

Release
To deploy an application to end users through Android Market or through other means, you must define the signing options.

Keystore Location
Enter the directory location of the keystore that contains the private key.

Keystore Password
Enter the password for the keystore.

Key Alias
Enter an alias for the key. Only the first eight characters of the alias are used.

Key Password
Enter the password for the key.