react-native: [0.45.0] Android release build failed

After updating to new version release build failed. Any ideas how does this fix?

FAILURE: Build failed with an exception.

* What went wrong:
Could not list contents of '/Users/vomchik/Projects/LITS/toolook/toolook-app-react-native/node_modules/react-native/third-party/glog-0.3.4/test-driver'. Couldn't follow symbolic link.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 35
  • Comments: 16 (10 by maintainers)

Commits related to this issue

Most upvoted comments

This worked for me: to delete the broken test-driver-link as follows

unlink node_modules/react-native/third-party/glog-0.3.4/test-driver

@hramos Not every issue should require all details to be filled out before it’s looked into…it’s not always something you can document the steps for in order to reproduce. Closing a genuine issue because it doesn’t meet your guidelines is pretty poor form.

This issue is closed. If this is still affecting you, please open a new issue and make sure to fill out everything in the template as documented in the contribution guidelines. Thanks!

I have the same error. Cleaning the node_modules works for me but the error reappears after every Xcode build.

It seems that the script ios-install-third-party.sh recreates the third-party folder with its content in node_modules/react-native.

The symbolic link mentioned in the error: node_modules/react-native/third-party/glog-0.3.4/test-driver'. Couldn't follow symbolic link. should point to automake test-driver -> /usr/share/automake-1.14/test-driver which does not exist in my case. I did reinstall xcode devtools but it didn’t solve the issue.

Can it be a wrong xcode setup/install on my side? I don’t want to clean the folder between android and ios builds every times.

Xcode 8.3.3

Same problem here, it happens to me when I try to build a release APK for Android at the :app:bundleReleaseJsAndAssets step.

As a temporary solution deleting the whole node_modules folder and re-installing dependencies fixes it.

My goal here is to get the issue tracker into a better state. There aren’t enough people following up and submitting PRs to fix the existing set of open issues. Opening a new issue without providing a minimum level of details is not helping out. I’m happy to reconsider the guidelines once the number of outstanding issues is in better shape. Thanks for understanding.

Hey, thanks for reporting this issue!

It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.

I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

I use a Makefile that points its clean target to a full clean script. I have found most issues like this can be solved by killing all simulators, packagers, etc, running clean, then reinstalling node_modules:

clean.sh

watchman watch-del-all
rm -rf node_modules
rm -rf $TMPDIR/react-*

@Guardiannw see my earlier comment.

Also having exact same issue. Solution provided by @olivierkaisin seems to work, but it is indeed frustrating having to delete node_modules at each build.

same issue here! whats going on with latest react native release? is fully os issues in both platforms 😦

This is a problem. Please resolve this. It is very annoying