-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Debugger breaks the ability to interact with my app after upgrade #28531
Comments
I'm getting similar issues ``[Sun Apr 05 2020 18:18:13.475] BUNDLE ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1)Error: Unable to resolve module ./debugger-ui/debuggerWorker.d9da4ed7.js from : None of these files exist:
|
I'm having the same issue with 0.62.0 building for android.
|
Have the same issue "react-native": "0.62.0" |
I suggest two potential solutions to this:
I tried doing both of these and the debugger problem no longer appeared on my console. Cheers! :) |
That's problems with plugins inside app, in my case is upgrading RNRF |
@farhankassam2 that solution doesn't work for me either. |
I'm having the same issue, and if you try to init a new project it occurs too :/ |
Getting the same issue. |
Mee too getting the same issue. |
same here |
same for me P.S. I restarted my laptop and removed application from my phone. After that I ran |
same issue |
Nope, I still get the issue. |
same for me |
I found this answer on stack overflow useful. Hard reload solved my issue. |
Finally found a working approach since had this issue after upgrade to RN v0.62.0:
after the new RN packager was started observed that Fast Refresh is working as expected. |
Even i had same issue on RN0.62.2 none of the above suggestions helped.. i downgraded to RN0.61.5 and hopefully it is working fine will wait for this issue to get fixed to upgrade. |
This helped me |
I have same issue but I resolved it by changing the browser from google chrome to Firefox. When I open debugger in firefox the error is removed and It is working. |
Try to do this: |
Am still having that same issue |
For me, what fixed it was removing
from my babel.config.js. None of the other methods worked. No idea why this fixes it but hey, it works! |
@artemkhalygov Thank you. It's work 👍 |
Removing the application from my phone, saving changes to git, Not sure if it happens again, but I have a desktop and a laptop and that problem never occured on my laptop. Both run Windows 10 64-bit, Node and Chrome versions are the same, I haven't found any differences yet. Since switching the workstation is not a solution I'll keep searching. |
Maybe the problem was in
|
I spent hours on this, but I finally figured it out! As it turns out, my time between my phone and desktop were unsynced by a few seconds.
from this comment However, a few things:
The solution for me wasn't to sync the time manually, but to set the NTP servers (which server tells your device what time it is) to match my Windows machine:
(Side note, if you're not certain that this is your time server, you can confirm by running this in PowerShell |
for me, I restarted my mac, it solved the issue |
Hi @crutchcorn, I checked you solution and for combination (Mac, Android Galaxy S8, react-native 0.62.2) it didn't help, unfortunately. Though I didn't try actually, because my devices seem to be in sync, but having same issues (ui-debugger missing ... + on device when debugging onPress events don't fire):
|
Yeah, @vsheyanov there definately seems to still need to be work done on this issue. While I can debug and press items on screen, the |
The trick I linked no longer works for me. It did for a time but is hit-or-miss whether or not it functions as-expected |
me too with RN 0.62.2. It just happened a few hours ago and the app in Android emulator stuck by the error. |
I have the same issue with RN 0.63.0. Tried to hard reset cache of chrome without any change. Also tried the It also does not matter if I run on emulator or on my device. Still getting |
Indeed this seems to fix it : https://stackoverflow.com/questions/59658998/expo-unable-to-resolve-module-debugger/60755519#60755519 just 'CMD+CTRL' and click reload button in chrome and then 'Reset cache & hard reload' |
Run npm i react-devtools-core in order to update debugger. |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
This issue was closed because it has been stalled for 7 days with no activity. |
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
Upon upgrading from
0.61.5
to0.62.1
, I noticed that whenever I try to run my debugger, I'm no longer able to interact with the app. When I open the debugger, I get the following error in the metro server:React Native version:
Run
react-native info
in your terminal and copy the results here.Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
yarn android
Expected Results
Describe what you expected to happen.
Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
https://github.com/crutchcorn/GitShark/tree/97ee89fc25c51a5ed03e59b25ee7967c1aea0211
The text was updated successfully, but these errors were encountered: