Skip to content

Executing "tns run android" fails to deploy app on default emulator #1689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pkoleva opened this issue Apr 18, 2016 · 1 comment
Closed

Executing "tns run android" fails to deploy app on default emulator #1689

pkoleva opened this issue Apr 18, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@pkoleva
Copy link
Contributor

pkoleva commented Apr 18, 2016

Emulator: default; latest android updates; API 23;
Steps to reproduce: Executing tns run android when no android emulator is opened fails to deploy app
Output: https://gist.github.com/pkoleva/ce94f9837725c4c9aa2103b5d103751f

@vchimev
Copy link

vchimev commented Apr 22, 2016

The tns run android command starts the emulator and exits without deploying the app.

Output:

mcsofvchimev:appJS vchimev$ tns run android
Copying template files...
  ◠ Installing tns-androidbabel-traverse@6.7.6 node_modules/babel-traverse
├── babel-messages@6.7.2
├── globals@8.18.0
├── babylon@6.7.0
├── debug@2.2.0 (ms@0.7.1)
├── babel-types@6.7.7 (to-fast-properties@1.0.2, esutils@2.0.2)
├── invariant@2.2.1 (loose-envify@1.1.0)
├── repeating@1.1.3 (is-finite@1.0.1)
├── babel-code-frame@6.7.7 (js-tokens@1.0.3, esutils@2.0.2, chalk@1.1.3)
├── lodash@3.10.1
└── babel-runtime@5.8.38 (core-js@1.2.6)
  ◠ Installing tns-androidbabel-types@6.7.7 node_modules/babel-types
├── to-fast-properties@1.0.2
├── esutils@2.0.2
├── lodash@3.10.1
└── babel-runtime@5.8.38 (core-js@1.2.6)
  ◝ Installing tns-androidbabylon@6.7.0 node_modules/babylon
└── babel-runtime@5.8.38 (core-js@1.2.6)
  ◝ Installing tns-androidfilewalker@0.1.2 node_modules/filewalker
└── fqueue@0.0.0
  ◟ Installing tns-androidlazy@1.0.11 node_modules/lazy
Project successfully created.
Starting Android emulator with image Emulator-Api23-Default
mcsofvchimev:appJS vchimev$ 

Output with log trace:

...
Using Android SDK '23'.
  ◡ Installing tns-androidDirectories to clean:
[]
execFile: /Users/vchimev/Library/Android/sdk/platform-tools/adb "help"
  ◞ Installing tns-androidbabel-traverse@6.7.6 node_modules/babel-traverse
├── babel-messages@6.7.2
├── globals@8.18.0
├── babylon@6.7.0
├── debug@2.2.0 (ms@0.7.1)
├── babel-types@6.7.7 (to-fast-properties@1.0.2, esutils@2.0.2)
├── invariant@2.2.1 (loose-envify@1.1.0)
├── repeating@1.1.3 (is-finite@1.0.1)
├── babel-code-frame@6.7.7 (js-tokens@1.0.3, esutils@2.0.2, chalk@1.1.3)
├── lodash@3.10.1
└── babel-runtime@5.8.38 (core-js@1.2.6)
  ◜ Installing tns-androidbabel-types@6.7.7 node_modules/babel-types
├── to-fast-properties@1.0.2
├── esutils@2.0.2
├── lodash@3.10.1
└── babel-runtime@5.8.38 (core-js@1.2.6)
  ◜ Installing tns-androidbabylon@6.7.0 node_modules/babylon
└── babel-runtime@5.8.38 (core-js@1.2.6)
  ◠ Installing tns-androidfilewalker@0.1.2 node_modules/filewalker
└── fqueue@0.0.0
  ◜ Installing tns-androidlazy@1.0.11 node_modules/lazy
Existing AndroidManifest.xml is correct.
Project successfully created.
startLookingForDevices; platform is Android
spawn: /Users/vchimev/Library/Android/sdk/platform-tools/adb "start-server"
spawn: /Users/vchimev/Library/Android/sdk/platform-tools/adb "devices"
execFile: /Users/vchimev/Library/Android/sdk/platform-tools/adb "devices"
Starting Android emulator with image Emulator-Api23-Default
spawn: /Users/vchimev/Library/Android/sdk/tools/emulator "-avd" "Emulator-Api23-Default"
execFile: /Users/vchimev/Library/Android/sdk/platform-tools/adb "devices"
execFile: /Users/vchimev/Library/Android/sdk/platform-tools/adb "devices"
mcsofvchimev:appJS vchimev$ 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants