react-native: Stuck in "Scanning folders for symlinks in..."

problem seems solved after closing and opening the terminal and running the command

Upgrade the react-native package

react-native upgrade After doing this *Make sure you are connected to the internet **Bcz when you run the app for the first time it will download the gradle dependency

react-native run-android *This command itself downloads all the gradle dependency

This method 100% works

The issue is simply because of some previous process which wouldn’t have been properly terminated before. for ubuntu just find the process using sudo lsof -i:8081 terminate the process by sudo -9 kill <your-process-id>

windows users can try by running cmd as admin then netstat -ano | findstr :8081 terminate the process by taskkill /PID <your-process-id> /F

hope this works cheers 😃

Update: It’s works well with ; Expo’s npm start and press a key to open emulator

But react-native run-android not working.

npm start
react-native run-android

I don’t think that’s a solution. 😃 We may need a reasonable explanation of the cause of this bug.

i solve the problem like this

1. terminal 1 : npm start (wait utiil start)
2. terminal2 : react-native run-android

“Restarting” is not a solution. Must have a rational explanation.

Has this issue been addressed by any of the developers? It seems to be active and its something that is bothering a lot of users. Can we please get an update / some assistance?

Thanks

I have the same issue on Ubuntu

When I ran react-native upgrade command, CMD says me;

Successfully upgraded this project to react-native v0.52.0
PS C:\Users\Furkan\AwesomeProject> react-native -v
react-native-cli: 2.0.1
react-native: 0.52.0

Edit: Same with npm install -g react-native-git-upgrade

@Dentrax you need to initialize the project first, following this steps cd C:\Users\Furkan react-native init AwesomeProject cd AwesomeProject react-native run-android

It looks like it’s packager running in the background is what causes this, closing the packager terminal will then correct the problem and restart packager.

I have the same problem on Windows 10 and React Native version 0.55.4

The problem for me was that the Metro Bundler (The window with title ‘node “…\local-cli\cli.js” start’) was open in the background from a previously terminated build.

After I closed that window, the new build process was able to spawn a new Metro Bundler and all proceeded fine from there.

Thanks for posting this! It looks like your issue may refer to an older version of React Native. Can you reproduce the issue on the latest stable release?

Thank you for your contributions.

_{How to Contribute • What to Expect from Maintainers}