React-native: Link fails

[stilllife00]

Description

Trying to link libraries (after adding react-native-config and after a full upgrade)

Reproduction

   react-native link

Result

  rnpm-install ERR! ERRPACKAGEJSON No package found. Are you sure it's a React Native project?  
  Cannot read property 'replace' of undefined

Solution

The package.json is there so the link should work

Additional Information

• React Native version: "react-native": "^0.41.1",
• Platform: Android (but I guess is irrelevant)
• Operating System: Linux Ubuntu 16.10

[j2kun]

I'm experiencing a similar issue with react-native-config:

$ react-native link react-native-config
rnpm-install info Android module react-native-config is already linked 
rnpm-install info Linking react-native-config 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

[SandroMachado]

I am experiencing the same issue with react-native-snackbar. Any fix for this?

[j2kun]

@SandroMachado My fix was to manually link

[SandroMachado]

I did the same :(

[j2kun]

@SandroMachado It's sad that the more I work with react native, the more problems I find with the tooling.

[tminard]

Same issue. What is going on? I am having to manually link for now.

react-native-cli: 2.0.1
react-native: 0.43.3

[tminard]

@stilllife00 I think I may have found it. My issue was due to a missing package name in my debug AndroidManifest.xml file. Ensure your manifests have a valid package="com." attribute:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.<package>">

...

</manifest>

Your issue may be different, since it appears the cli just try...catch the whole loading process and throws this vague error if anything goes wrong. Here's the actual code that gave me a problem:

local-cli/core/android/index.js

L17: const getPackageName = (manifest) => manifest.attr.package; // <- Assumes package name attribute

…

L40: const packageName = userConfig.packageName || getPackageName(manifest);
  const packageFolder = userConfig.packageFolder ||
    packageName.replace(/\./g, path.sep); // <- Not nil safe

[stilllife00]

@tminard That actually did the trick. I was entirely missing the package attribute from the src/debug/AndroidManifest.xml

[fabriziomoscon]

I had the same issue. Adding package to all AndroidManifest.xml files fixed it.

This issue can be closed

[hramos]

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.

[bjacog]

I was experiencing the same issue. Turns out the developer had commented out the whole manifest and wrote the new manifest in the same file with the old version commented out at the bottom causing the same issue. I guess it is because of the package="com." string being present more than once in the file.

[dancherb]

Cheers @bjacog, happened for me because I had something commented out at the bottom of my manifest (though not to do with package).