Skip to content

Latest commit

 

History

History
72 lines (62 loc) · 6.02 KB

run-android.md

File metadata and controls

72 lines (62 loc) · 6.02 KB

run android

Usage Synopsis
Run on all connected devices and running emulators $ tns run android [--key-store-path <File Path> --key-store-password <Password> --key-store-alias <Name> --key-store-alias-password <Password>] [--release] [--justlaunch]
Run on a selected connected device or running emulator $ tns run android --device <Device ID> [--key-store-path <File Path> --key-store-password <Password> --key-store-alias <Name> --key-store-alias-password <Password>] [--release] [--justlaunch]
Start an emulator and run the app inside it $ tns run android --emulator [<Emulator Options>] [--key-store-path <File Path> --key-store-password <Password> --key-store-alias <Name> --key-store-alias-password <Password>] [--release] [--justlaunch]

Runs your project on a connected Android device or in a native Android emulator, if configured. This is shorthand for prepare, build and deploy. While your app is running, prints the output from the application in the console.

Options

  • --device - Specifies a connected device on which to run the app.
  • --emulator - If set, runs the app in a native emulator for the target platform, if configured. When set, you can also set any other valid combination of emulator options as listed by $ tns help emulate android.
  • --release - If set, produces a release build. Otherwise, produces a debug build. When set, you must also specify the --key-store-* options.
  • --key-store-path - Specifies the file path to the keystore file (P12) which you want to use to code sign your APK. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
  • --key-store-password - Provides the password for the keystore file specified with --key-store-path. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
  • --key-store-alias - Provides the alias for the keystore file specified with --key-store-path. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
  • --key-store-alias-password - Provides the password for the alias specified with --key-store-alias-password. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
  • --justlaunch - If set, does not print the application output in the console.

Attributes

  • <Device ID> is the index or name of the target device as listed by $ tns device android
  • <Emulator Options> is any valid combination of options as listed by $ tns help emulate android

<% if(isHtml) { %>

Prerequisites:

Before running your app in the Android emulator from the Android SDK, verify that your system meets the following requirements.

  • Verify that you have installed the Android SDK.
  • Verify that you have added the following Android SDK directories to the PATH environment variable:
    • platform-tools
    • tools
  • Before running your app in the Genymotion emulator, verify that your system meets the following requirements.
    • Verify that you have installed Genymotion.
    • On Windows and Linux systems, verify that you have added the Genymotion installation directory to the PATH environment variable.
    • On OS X systems, verify that you have added the following paths to the PATH environment variable.
      • For Genymotion earlier than 2.6:
        • /Applications/Genymotion.app/Contents/MacOS/
        • /Applications/Genymotion Shell.app/Contents/MacOS/
      • For Genymotion 2.6:
        • /Applications/Genymotion.app/Contents/MacOS/player.app/Contents/MacOS
        • /Applications/Genymotion Shell.app/Contents/MacOS/

Command Limitations

  • You cannot use --device and --emulator simultaneously.
  • When the --release flag is set, you must also specify all --key-store-* options.

Related Commands

Command Description
build android Builds the project for Android and produces an APK that you can manually deploy on device or in the native emulator.
build ios Builds the project for iOS and produces an APP or IPA that you can manually deploy in the iOS Simulator or on device, respectively.
build Builds the project for the selected target platform and produces an application package that you can manually deploy on device or in the native emulator.
debug android Debugs your project on a connected Android device or in a native emulator.
debug ios Debugs your project on a connected iOS device or in a native emulator.
debug Debugs your project on a connected device or in a native emulator.
deploy Builds and deploys the project to a connected physical or virtual device.
emulate android Builds the specified project and runs it in a native Android emulator.
emulate ios Builds the specified project and runs it in the native iOS Simulator.
emulate You must run the emulate command with a related command.
livesync Synchronizes the latest changes in your project to devices.
livesync ios Synchronizes the latest changes in your project to iOS devices or the iOS Simulator.
livesync android Synchronizes the latest changes in your project to Android devices.
run ios Runs your project on a connected iOS device or in the iOS Simulator, if configured.
run Runs your project on a connected device or in the native emulator for the selected platform.
test init Configures your project for unit testing with a selected framework.
test android Runs the tests in your project on Android devices or native emulators.
test ios Runs the tests in your project on iOS devices or the iOS Simulator.
<% } %>