Daniel Friesen 1ad08aa659 Fix react-native link issue when using multiple manifests ...

Summary:
`react-native link` often fails due to the wrong manifest being used when you use a debug manifest. `findManifest` returns `debug/AndroidManifest.xml` instead of `main/AndroidManifest.xml`. And the debug manifest usually does not have the package name defined so `projectConfigAndroid` throws a cryptic "Cannot read property 'replace' of undefined" error.

This fixes the issue by throwing a more user friendly error and providing a `manifestPath` userConfig.

This is mostly based on comments to #10050.
Closes https://github.com/facebook/react-native/pull/13373

Differential Revision: D4945690

Pulled By: shergin

fbshipit-source-id: b177f916fd4799c873d2515c18cbb87bef3203f0

2017-06-06 14:20:06 -07:00

..

findAndroidAppFolder.spec.js

Merge rnpm config with the cli config, step 1

2017-01-09 07:58:33 -08:00

findManifest.spec.js

Merge rnpm config with the cli config, step 1

2017-01-09 07:58:33 -08:00

findPackageClassName.spec.js

Merge rnpm config with the cli config, step 1

2017-01-09 07:58:33 -08:00

getDependencyConfig.spec.js

Merge rnpm config with the cli config, step 1

2017-01-09 07:58:33 -08:00

getProjectConfig.spec.js

Fix react-native link issue when using multiple manifests

2017-06-06 14:20:06 -07:00

readManifest.spec.js

Merge rnpm config with the cli config, step 1

2017-01-09 07:58:33 -08:00