-
Notifications
You must be signed in to change notification settings - Fork 266
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
Unable to resolve module ../Components/AccessibilityInfo/AccessibilityInfo
message
#1123
Comments
Hi @StasD and thanks for reaching us. The issue with RN 0.61 debugging is already resolved(#1122) and the fix will be released soon. With respect to Metro bundler problems I recommend you to clear your caches and let us know if that worked for you. You can use the following instruction:
|
Ran your commands. That didn't make any difference re: those |
@StasD I just tested
I noticed that there is no
|
Created a brand new project: |
Hi @StasD, I tried to reproduce that behavior on iPhone 11 Pro simulator and I didn't faced any problems. Could you please also try to clean
|
With the latest version of |
@StasD, could you please share a demo application where such a behavior is reproduced? It will help us to investigate your problem. |
Here is the url: https://stas-ie.s3-eu-west-1.amazonaws.com/public/MyApp.zip
Looks similar to the one you referenced above, I think. |
Hi @StasD . I was able to reproduce that behavior. Could you please try VSIX with a fix and let us know how it works for you? To try it please do the following:
|
Hi @SounD120, |
Thanks, @StasD ! Glad to hear that. Are you still experiencing issue with |
No, those messages also gone. You can close this issue, I suppose. |
I posted this bug to react-native a few days ago: facebook/react-native#26568
Probably it should instead be posted here, because when I run
react-native run-ios
, there are no such messages.Also, debugging in VSCode completely stopped working after upgrading to RN 0.61 ('unverified breakpoint')...
Software versions
The text was updated successfully, but these errors were encountered: