javascript - emulator stuck at loading from 10.0.2.2:8081,what is issue? - Stack Overflow

admin管理员组

文章数量:1339702

I am working on a react-native project and I run it on emulator android(AVD manager)

i have run adb reverse tcp:8081 tcp:8081 at cmd , but still my emulator stuck Whenever i am changing my project and reload emulator!

Development Operating System:Windows 10

React Native version: 0.55.4enter image description here

I am working on a react-native project and I run it on emulator android(AVD manager)

i have run adb reverse tcp:8081 tcp:8081 at cmd , but still my emulator stuck Whenever i am changing my project and reload emulator!

Development Operating System:Windows 10

React Native version: 0.55.4enter image description here

• javascript
• android
• react-native
• ecmascript-6

Share Improve this question Follow edited Jun 20, 2020 at 9:12 CommunityBot 111 silver badge asked Jul 31, 2018 at 22:25 MahdaviMahdavi 8122 silver badges77 bronze badges 2

• What is running at 10.0.2.2, and can the Android (Emulator) properly route packets to that address? – Matt Clark Commented Jul 31, 2018 at 22:28
• i don't know what is running at 10.0.2.2!!, when i am running react-native run-android ,it build successful – Mahdavi Commented Aug 1, 2018 at 8:37

Add a ment  | 

7 Answers 7

Sorted by: Reset to default 8

I had the same issue. I fixed it by reinstalling the watchman package. If you are using mac do this brew uninstall watchman and then brew install watchman

Maybe your 8081 port is already in use.

Try the first solution in here https://facebook.github.io/react-native/docs/troubleshooting

$ sudo lsof -i :8081

$ kill -9

After that,

$ cd YourProject

and

$ npm start

this should help you debugging the packager

echo 256 | sudo tee -a /proc/sys/fs/inotify/max_user_instances
echo 32768 | sudo tee -a /proc/sys/fs/inotify/max_queued_events
echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches

YEP, THAT'S IT.

I had this issue that watchman wasn't able to create the directory in /usr/local/var/run/watchman/-state. I granted access to the parent directory (probably not needed as it likely users system access) then I manually created the directory and re-ran it.

I got the path to the missing directory from the metro terminal window.

Worked fine after that.

The latest version of React Native change the port of emulator by somehow but the older not. Anyway, please reference to this link . Then it will help you sort it out.

Cheer!

Your issue can also relate to watchman, try the following mands (I used them on linux ubuntu)

   echo 256 | sudo tee -a /proc/sys/fs/inotify/max_user_instances
   echo 32768 | sudo tee -a /proc/sys/fs/inotify/max_queued_events
   echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches

the above mands worked for me

Solution for Ubuntu found here: https://reactnativeforyou./android-emulator-stuck-at-loading-from-10-0-2-28081-react-native-issue-fix/

echo 256 | sudo tee -a /proc/sys/fs/inotify/max_user_instances
echo 32768 | sudo tee -a /proc/sys/fs/inotify/max_queued_events
echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches
pkill node

本文标签： javascriptemulator stuck at loading from 100228081what is issueStack Overflow