Vscode-react-native: Can no longer debug iOS device

Created on 19 Oct 2017  ยท  4Comments  ยท  Source: microsoft/vscode-react-native

Actual Behavior

  1. Selecting my configuration for iOS device results in launching and debugging simulator

Expected Behavior

  1. debug on my iOS device

Here's my config:

    {
        "name": "Debug iOS device",
        "program": "${workspaceRoot}/.vscode/launchReactNative.js",
        "type": "reactnative",
        "request": "launch",
        "platform": "ios",
        "target": "device",
        "sourceMaps": true,
        "outDir": "${workspaceRoot}/.vscode/.react"
    },

This was working great when you first added the ability to use 'target: device'. Recent update seems to have broken this? I noticed 4.3 now depends on 'Node Debug 2'. I never noticed that before.

Software versions

  • React-Native VS Code extension version: 4.3
  • VSCode version: 1.17.2
  • OS platform and version: latest MacOS
  • NodeJS version:
  • React Native version: 0.49.1

Outputs (Include if relevant)

  • Output of the Debug Console (View -> Toggle Debug Console):
OS: darwin x64
Adapter node: v7.9.0 x64
vscode-chrome-debug-core: 3.17.3
Starting debugger app worker.
Established a connection with the Proxy (Packager) to the React Native application
Debugger worker loaded runtime on port 41266
(removed app specific debug from this point on)

  • Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):
[Info] Starting Packager

Scanning folders for symlinks in /Users/kralferch/source/visualstudio/mixer/node_modules (14ms)
 โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” 
 โ”‚  Running packager on port 8081.                                            โ”‚ 
 โ”‚                                                                            โ”‚ 
 โ”‚  Keep this packager running while developing on any JS projects. Feel      โ”‚ 
 โ”‚  free to close this tab and run your own packager instance if you          โ”‚ 
 โ”‚  prefer.                                                                   โ”‚ 
 โ”‚                                                                            โ”‚ 
 โ”‚  https://github.com/facebook/react-native                                  โ”‚ 
 โ”‚                                                                            โ”‚ 
 โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ 
Looking for JS files in
   /Users/kralferch/source/visualstudio/mixer 


React packager ready.

Loading dependency graph, done.
[Info] Packager started.

[Info] Prewarming bundle cache. This may take a while ...

[Info] About to get: http://localhost:8081/index.ios.bundle?platform=ios

Bundling `index.ios.js`  [development, non-minified]  100.0% (1480/1480), done.
[Warning] The Bundle Cache was prewarmed.

[Info] Building and running application.

[Info] About to search for plist in base folder: /Users/kralferch/Library/Developer/CoreSimulator/Devices/5D9BC56C-57E1-4126-B4EC-81057F3EE560/data/Containers/Data/Application pathAfter: Library/Preferences/com.mcprohosting.Beam.plist in each of the apps: 12A578E8-B244-4688-9634-3939D6408EFF,17703579-72E4-4D48-95EE-72B9AF09A77A,1BDDB227-FA44-45E8-B46A-3673AC0F3D86,221BF8E0-EF0C-4A0B-8E8B-24A26816D175,225045CC-EB70-4605-A5D1-935F1401A605,24C84858-8C60-4406-9154-2D1EAEF40520,3CA25425-5AA5-4424-8A4B-63240CBF2C3F,42C71E46-0C2A-40EF-88FA-E66E87B2BF16,4892E98C-4007-4DD9-A1E9-880CF7F09EA1,4F957C7C-35B5-4268-B163-3147A57A0914,50A08AD3-F20E-4911-8898-4A34AD4A9694,562569B1-7C4E-4E3F-BDB4-ACD18AB5E170,6741CB52-72C0-4BA9-9023-AEFB32A2A029,69851327-851B-4817-B675-3A2F14F33B52,73EF0AC1-3C49-487E-BC1E-2295BDF13C35,8707546B-C4DE-4521-8435-32F8485780E1,94E65CCC-B941-43D1-8DFB-2EEF0E6539FE,9747ECB1-BE00-4297-AD17-041F1A03459C,9E3B7DF9-E804-4ADF-AA8A-AED34878C628,A23E3D67-E3E2-4777-8361-F848C75101D4,A55294B2-3DFB-45C9-9151-D6B74E5DA3E6,ACB04ACC-75DE-4C0D-894E-A00E2E74D8E5,B0389CB6-203B-4C5E-8B31-826ADF2C4D06,B0667FAE-68CD-4603-8DB3-8FE3424960D7,B2F3A9C6-4DA3-463C-9B41-1BCC68C835FE,B35C7C52-C810-440B-9ED2-FE9626ACC28C,C0D40D12-73B1-48F0-8C76-DF98BE555802,C5833B0A-48C0-442E-ACEF-F3DE3E74922A,CE8F2A4D-9FF6-4C6C-91A0-7B7463E813A6,D5022AD2-7DF5-4A65-9947-AECE022E4146,D8BDE66F-704F-4758-907E-67670C206D79,E5532A59-123D-4567-8191-E5143F309DA8,FC9B1562-F6A8-4372-B914-212441A20B8B

Starting custom debugger by executing: echo A debugger is not needed:  "/Users/kralferch/source/visualstudio/mixer"
Bundling `index.ios.js`  [development, non-minified]  100.0% (1480/1480), done.
  • Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):
extensionService.ts:435 Overwriting extension /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.node-debug2 with /Users/kralferch/.vscode/extensions/ms-vscode.node-debug2-1.18.3.
e._logMessageInConsole @ extensionService.ts:435
console.ts:123 [Extension Host] (node:15234) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ console.ts:123
bug triaged

All 4 comments

Hi @kralcifer-ms
We have always used 'Node Debug 2'.

Could you please copy output of the React Native: Run iOS output channel (View -> Output -> Select React Native: Run iOS in ListBox).
Thanks!

I found problem

I verified that 4.4 fixes it. Thanks for the quick turnaround!

Is it possible to change the default port from 8081 to something else?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Jacky9425 picture Jacky9425  ยท  4Comments

joshuaskelton picture joshuaskelton  ยท  6Comments

kevinnguy picture kevinnguy  ยท  3Comments

molant picture molant  ยท  3Comments

SounD120 picture SounD120  ยท  4Comments