Skip to content
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

react-native link occasionally errs with "str.replace is not a function", no way to debug #12940

Closed
j2kun opened this issue Mar 14, 2017 · 2 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@j2kun
Copy link

j2kun commented Mar 14, 2017

Description

I have an xcode workspace set up with nonstandard configurations, and adding a new react-native ios dependency sometimes fails with str.replace is not a function. I have no idea how to debug this, as the linking command doesn't provide a --verbose option, or anything similar.

E.g.

react-native link react-native-image-crop-picker
rnpm-install info Android module react-native-image-crop-picker is already linked 
rnpm-install info Linking react-native-image-crop-picker ios dependency 
rnpm-install ERR! It seems something went wrong while linking. Error: str.replace is not a function 
Please file an issue here: https://github.com/facebook/react-native/issues 

str.replace is not a function

I cannot reproduce this issue from a fresh project install, and I have no idea where to look for the problem.

react-native-cli: 2.0.1
react-native: 0.40.0
@dantman
Copy link
Contributor

dantman commented Apr 28, 2017

I fixed one instance of this type of error in #13373 where .replace was called on packageName when it can be undefined.

If you want to dig into the source of an error in link you can dump the error to the console from here:

return promiseWaterfall(tasks).catch(err => {
log.error(
`Something went wrong while linking. Error: ${err.message} \n` +
'Please file an issue here: https://github.com/facebook/react-native/issues'
);
throw err;
});

@hramos
Copy link
Contributor

hramos commented Jul 25, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Jul 25, 2017
@hramos hramos closed this as completed Jul 25, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Jul 25, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants