react-native link hangs after "Assets have been successfully linked to your project"

[rendomnet]

• [x] I have reviewed the documentation
• [x] I have searched existing issues
• [x] I am using the latest React Native version

after running
react-native link

Scanning folders for symlinks in /Users/appfolder/node_modules (12ms)
rnpm-install info Platform 'ios' module react-native-firebase is already linked
rnpm-install info Linking react-native-firebase android dependency
rnpm-install info Platform 'android' module react-native-firebase has been successfully linked
rnpm-install info Platform 'ios' module react-native-image-crop-picker is already linked
rnpm-install info Linking react-native-image-crop-picker android dependency
rnpm-install info Platform 'android' module react-native-image-crop-picker has been successfully linked
rnpm-install info Linking react-native-localization ios dependency
rnpm-install info Platform 'ios' module react-native-localization has been successfully linked
rnpm-install info Linking react-native-localization android dependency
rnpm-install info Platform 'android' module react-native-localization has been successfully linked
rnpm-install info Platform 'ios' module react-native-maps is already linked
rnpm-install info Linking react-native-maps android dependency
rnpm-install info Platform 'android' module react-native-maps has been successfully linked
rnpm-install info Platform 'ios' module react-native-vector-icons is already linked
rnpm-install info Linking react-native-vector-icons android dependency
rnpm-install info Platform 'android' module react-native-vector-icons has been successfully linked
rnpm-install info Linking assets to ios project
rnpm-install info Linking assets to android project
rnpm-install info Assets have been successfully linked to your project
^^^^
stuck here.

Environment

Environment:
OS: macOS High Sierra 10.13.4
Node: 8.9.1
Yarn: 1.6.0
npm: 6.1.0
Watchman: Not Found
Xcode: Xcode 9.3 Build version 9E145
Android Studio: 3.1 AI-173.4697961

Packages: (wanted => installed)
react: 16.3.2 => 16.3.2
react-native: 0.55.4 => 0.55.4

also I'm using
classpath 'com.android.tools.build:gradle:3.1.2'
classpath 'com.google.gms:google-services:3.2.1'

Expected Behavior

succesfull linking

Actual Behavior

console stuck.

What can cause this, where to look first?

[react-native-bot]

Please use Stack Overflow for this type of question.

[simontabor]

I have this exact same issue, and it feels like an issue with react-native-git-upgrade. Upgrading from 0.44 to either 0.48 or 0.55 hangs at rnpm-install info Assets have been successfully linked to your project but yarn install succeeds (including rnpm).

Why has this been assigned as a Stack Overflow question?

[EricMcRay]

I have the same problem. I upgraded from 0.49 to 0.55 with react-native-git-upgrade.

[hubsmoke]

I have the same problem

[MacKentoch]

I did just create a fresh project (30minutes ago) with react-native init __MY_PROJECT_NAME__ and I also have this issue.

[ramyareye]

+1

[assyme]

Same issue. Upgraded using react-native-git-upgrade

[Jake8K]

+1

[tendolukwago]

Any reason why this is labeled as closed?

[Jake8K]

I don't know, but it was 'react-native-fetch-blob' that was causing it to hang on my machine. If I don't include that in my package.json it doesn't hang.

[gkpo]

Same issue here, just created a fresh project with react-native init

[falconmick]

same issue

[falconmick]

Ok after cloning the react-native repo, setting up sinopia to get local dev working (oh boy was that painful) turns out the issue is that commander.js is not returning on complete, if you hit enter it terminates the task and then it works.

The fix is to find out how to make this automatically return upon completion without hitting enter.

[zoozalp]

Upgrading to node 10 resolves the issue for me.

[techopsway2b1]

This is a serious issue and needs to be addressed on this thread and not stackoverflow. The command will hang on random processes. Im still investigating if this is a non-interactive shell vs. interactive shell problem, but its clearly an issue within the the react-native link CLI call. I see this occuring more frequently from remote SSH calls to scripts invoking the react-native link CLI call vs. running the same script locally, but most of us want to automate our tasks for building from a build server and this is breaking that process. Can someone from Facebook or this project's community address this issue.... PLEASE!!!