Visitar URL original
Breakpoints do not get hit work with while debugging react native app · Issue #928 · microsoft/vscode-react-native · GitHub
Skip to content

Breakpoints do not get hit work with while debugging react native app #928

Closed
Closed
Breakpoints do not get hit work with while debugging react native app#928
Labels
debuggerexternalresolved

Description

@MarcoLLeite
Marco Leite (MarcoLLeite)
opened on Mar 8, 2019

Actual Behavior

  1. The debugger seems to work and connect, but I never get a hit on any breakpoints.

Expected Behavior

  1. Connect debugger and breakpoint getting a hit

Software versions

  • Windows 10 and Windows 7 ( I have tried one 2 machines)
  • React-Native VS Code extension version:
  • VSCode version: 1.31.1, 1.32.1, 1.32.3
  • OS platform and version: android 8.0 (emualtor and device)
  • NodeJS version: 10.14.2, 11.13.0
  • React Native version: 0.58.5, 0.58.6
  • react-native-cli: 2.0.1
  • Expo SDK version (include if relevant): not using expo

Outputs (Include if relevant)

  • Output of the Debug Console (View -> Toggle Debug Console):
OS: win32 x64
Adapter node: v10.2.0 x64
vscode-chrome-debug-core: 6.7.40
Starting debugger app worker.
Established a connection with the Proxy (Packager) to the React Native application
Debugger worker loaded runtime on port 9330
Running application "FinanceA" with appParams: {"rootTag":211}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF
index.bundle:46920
Debugger worker loaded runtime on port 12389
Running application "FinanceA" with appParams: {"rootTag":221}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF

PASTE OUTPUT HERE

- Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):

PASTE OUTPUT HERE

- Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):

PASTE OUTPUT HERE


This started to happen when I installed the version 1.31.1 more then a week ago. Installing the latest version 1.32.1 does not seem to fix this issue either.
I am not sure if this is directly related to any version as installing previous version does not seem to fix the issue.

Before that it used to work perfectly on both android emulators and android devices. Now it happens while debugging both android emulators and actual devices.

Any suggestions? Ideas?

Activity

  1. SounD120 commented on Mar 11, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Mar 11, 2019
    Contributor

    Hi Marco Leite (@MarcoLLeite) , thanks for reaching us. Could you please provide a small demo of your app for better understanding from our side? Also could you please fill up outputs using the template below?

    • Output of the Debug Console (View -> Toggle Debug Console):
    PASTE OUTPUT HERE
    • Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):
    PASTE OUTPUT HERE
    • Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):
    PASTE OUTPUT HERE

    Also it would be great if you add operational system on which you facing this.
    Also please make sure that Remote JS Debug is enabled on your device/emulator, we have instructions for enabling that setting in our README.

  2. Yuri Skorokhodov (SounD120)
    added
    waiting-for-clarification
    need-more-info
    need-repro
    and removed
    waiting-for-clarification
    need-repro
    on Mar 11, 2019

  3. SounD120 commented on Mar 14, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Mar 14, 2019
    Contributor

    Hi Marco Leite (@MarcoLLeite) . Do you have a chance to look at this?

  4. SounD120 commented on Mar 19, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Mar 19, 2019
    Contributor

    Hi Marco Leite (@MarcoLLeite) . I'm closing this due to inactivity, feel free to reopen the issue and provide additional information if you still facing this problem.

  5. Yuri Skorokhodov (SounD120)
    closed this as completedon Mar 19, 2019

  6. MarcoLLeite commented on Mar 30, 2019

    @MarcoLLeite
    Marco Leite (MarcoLLeite)
    on Mar 30, 2019
    Author

    Hi Yuri Skorokhodov (@SounD120) ,

    Sorry, but haven't got much time up until now.
    Yes the issue is still happening, and now it also happens to all my co-workers.

    I have a create a new repo under my account "FinanceA", you can use test to replicate it (I have temporarely added you as a collaborator, so you can access it).
    https://github.com/MarcoLLeite/FinanceA
    I am runing on Windows 7 Ultimate (but it also happens in my surface with Windows 10 - all details about SW versions are on description above).

  7. Yuri Skorokhodov (SounD120)
    reopened this on Mar 30, 2019
  8. Yuri Skorokhodov (SounD120)
    added
    investigating
    and removed
    need-more-info
    on Apr 1, 2019

  9. SounD120 commented on Apr 1, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Apr 1, 2019
    Contributor

    Hi Marco Leite (@MarcoLLeite) I just tested your application and all breakpoints that I set were hit. Could you please add "trace": "verbose" to your debug configuration, run your application and send the outputs here (by the templates I described above), or via email(v-yuskor@microsoft.com) if you think that they would contain private informaton? Also, could you please describe which exact BPs are not working (point to the files and lines of code)? Also, do you use any custom packagers (Haul, etc)?

  10. Yuri Skorokhodov (SounD120)
    added
    waiting-for-clarification
    on Apr 1, 2019

  11. 7 remaining items

  12. SounD120 commented on Apr 4, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Apr 4, 2019
    Contributor

    Marco Leite (@MarcoLLeite) Matheus de Assis Caetano (@macaetano) Thanks a lot for your clarifications. Finally I was able to reproduce that, and now starting to work on a fix. As I found out Debug Android debug scenario is not affected by this bug, so you can use it until new version is released.

  13. Ruslan Bikkinin (ruslan-bikkinin)
    added
    debugger
    on Apr 4, 2019

  14. SounD120 commented on Apr 4, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Apr 4, 2019
    Contributor

    Hi Marco Leite (@MarcoLLeite) . After further investigation I found out that there is no such problems on React Native 0.57.7 and 0.59.3, so could you please try to bump React Native dependencies as shown below:

    "react": "^16.8.3",
"react-native": "^0.59.3",

    and let us know if you still experience such problems?

  15. Yuri Skorokhodov (SounD120)
    added
    waiting-for-clarification
    external
    and removed
    bug
    on Apr 4, 2019

  16. MarcoLLeite commented on Apr 5, 2019

    @MarcoLLeite
    Marco Leite (MarcoLLeite)
    on Apr 5, 2019
    Author

    Hi Yuri Skorokhodov (@SounD120),

    Thanks for all your help. I had forgotten to let you know yesterday, but I got the Attach to Process working on VS Code on my Windwos 7 machine by bumping react-native to 0.59.3 (and kept react in version 16.6.3) and with the help of this:
    mergeResourcesProvider issue.

    I had downgraded from 0.59.3 to 0.58.5, because 0.59.3 was not even building for me, so I went back to the version that seemed more stable (0.58.5), at least on the other project it was building.

    Soon I will also update to "react 16.8.3" too, unless it brings other issues.

    I will try to use "Debug Android" and try to upgrade react-native on my other project on thesurface with Windows 10 as soon as possible and will let you know (probably happening tomorrow).

  17. SounD120 commented on Apr 10, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Apr 10, 2019
    Contributor

    Hi Marco Leite (@MarcoLLeite) . Are you still experiencing issues with debugging or they are gone after update?

  18. MarcoLLeite commented on Apr 11, 2019

    @MarcoLLeite
    Marco Leite (MarcoLLeite)
    on Apr 11, 2019
    Author

    Hi Yuri Skorokhodov (@SounD120). Thanks for the help... Yes, after upgrading to 0.59.3 the debugger seems to be back up hitting breakpoints... I haven't said anything because he are still resolving issues related with the upgrade. But that fixed the debugger anyway.

    Thanks.

  19. Marco Leite (MarcoLLeite)
    closed this as completedon Apr 11, 2019
  20. Yuri Skorokhodov (SounD120)
    added
    resolved
    and removed
    waiting-for-clarification
    on Apr 11, 2019

  21. MarcoLLeite commented on Apr 12, 2019

    @MarcoLLeite
    Marco Leite (MarcoLLeite)
    on Apr 12, 2019
    Author

    Just to point out a few more details of what happens:

    On my old version of react-native non of the debugger options would work, no breakpoints would get hit ('Debug Android' and 'Attach to Packager' options).
    I only updated react-native to 0.59.3 and kept react on 16.6.3 and both options started to work.
    I will also update react, because it triggers warnings on build, but wanted to point out that just updating one helped.

  22. SounD120 commented on Apr 12, 2019

    @SounD120
    Yuri Skorokhodov (SounD120)
    on Apr 12, 2019
    Contributor

    Marco Leite (@MarcoLLeite) Thanks for information! I think we'll add information about possible problems with React Native 0.58.* in our documentation.

  23. h0nor commented on Jun 18, 2019

    @h0nor
    Serdar O. (h0nor)
    on Jun 18, 2019
    • Output of the Debug Console (View -> Toggle Debug Console):

    I was having the same problem. Checking the output of the debug console led me in the right direction and I was able to fix the problem.

    Cheers Yuri Skorokhodov (@SounD120)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    debuggerexternalresolved

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions