Vscode-react-native: White screen on iOS simulator after running Attach to debugger configuration

Created on 17 Jul 2017  ยท  6Comments  ยท  Source: microsoft/vscode-react-native

Actual Behavior

  1. Nothing is showing on the simulator after running Attach to debugger configuration and selecting Remote JS Debugging on the device menu.
    The break points are active.
    Only the pause, restart and disconnect buttons are active in VS Code.

Expected Behavior

  1. A button and a text view appear.
    When I press the button, a number increments and is shown in the text view and I can debug the application on the iOS simulator.

Software versions

  • React-Native VS Code extension version: 0.3.2
  • VSCode version: 1.13.1
  • OS platform and version: Sierra 10.12.5
  • NodeJS version: 8.1.4
  • React Native version: 0.46.1

Outputs (Include if relevant)

  • Output of the Debug Console (View -> Toggle Debug Console):
[vscode-react-native] Debugger ready. Enable remote debugging in app.
[vscode-react-native] Starting debugger app worker.
[vscode-react-native] Established a connection with the Proxy (Packager) to the React Native 
application

After selecting Remote debugger in the simulator menu, this displays in the Debug Console:
[vscode-react-native] Debugger worker loaded runtime on port 32719
  • Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):
React-Native doesn't appear in the ListBox.
But this is what I get from the packager:

Scanning 559 folders for symlinks in /Users/lorand/React/Test/node_modules (93ms)
 โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” 
 โ”‚  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/lorand/React/Test 


React packager ready.

Loading dependency graph, done.
Bundling `index.ios.js`  100.0% (301/301), done.
  • Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):
[Extension Host] (node:875) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
But this error is not reproducing all the time. I tried to reproduce it but I can't.
bug duplicate triaged

Most helpful comment

In vscode store ,version of tool is still 0.32.

When do you go to the release?

I'm new to here.

Thanks.

All 6 comments

@LorandP this looks like a dupe of #459 and has been already fixed in #465

In vscode store ,version of tool is still 0.32.

When do you go to the release?

I'm new to here.

Thanks.

@RoJoHub soon :) Sorry for delay guys, we're working on it.

/cc @panarasi

Closing this as a dupe

Would be great to have this soon, as it's really affecting productivity a lot. A developer without a debugger is like a fish without water...

@RobIsHere
Where are u from?,I'm from china.
Your launguaue mode is like chinese.
haha.
:)

Was this page helpful?
0 / 5 - 0 ratings