If you think this is a driver issue, please try Where do we see webstorm64.exe ? Let try to run a system scan with Speed Up My PC to see any error, then you can do some other troubleshooting steps. If you encounter difficulties with webstorm64.exe, you can uninstall the associated program (Start > Control Panel > Add/Remove programs Let try the program named DriverIdentifier to see if it helps. It would have been good if I could skip steps 1 and 2 for debugging expo projects, but as of WebStorm 2020.2 this is not possible.Is webstorm64.exe using too much CPU or memory ? It's probably your file has been infected with a virus. no need of steps 1 and 2 for non-expo projects. However, if I debug a normal non-expo react-native project in WebStorm, then a break point in WebStorm will be hit without having to set break point in debugger's chrome instance dev tools i.e. Also, at the same time in WebStorm the same break point as in chrome dev tools will be hit, and from this point onward developer can either debug in chrome dev tools or in WebStorm. When expo app reloads in android emulator, then automatically the code will break at break points set in step (2) above. (3) Click on Reload button in debugger's chrome instance (2) Set one or more break points in App.js and/or custom components (this must be done in chrome dev tools instance that was opened in step 1 and NOT in your cod editor/IDE) (1) Open Dev Tools in debugger's chrome instance For expo project debugging to work in WebStorm, the following steps needs to be done.
There are some important points to note when debugging expo project in WebStorm. I was able to finally debug an expo react-native project in WebStorm.
0 kommentar(er)
