Android Manifest not found during linking with rnpm phase #138
Comments
|
Checking on this now |
|
I can't recreate this. Can you verify you have the latest
Also, verify you have the latest released ignite. 0.3.1 |
|
Additionally, can you verify that your AndroidManifest file exists or does not exist in the directory it is looking? |
|
Running into the same with: // reinstalling react-native-ignite fixed the problem. |
|
Hrmmm odd! @evanmrose - did you try re-installing ignite? @hknd, what version was Ignite when you first installed it? Maybe this is an upgrade issue? |
|
@GantMan my first version was prolly 0.3.x. I did an upgrade to 0.4.0 and then I encountered that error. (then I resolved it via uninstall+install) |
|
thanks! It must have been some kind of upgrade limbo. I'll close this ticket for now. We'll revisit if we get anyone with this issue again. |
|
I'm having the same problem. Tried reinstalling, didn't help.
|
|
can you verify that the identified file exists? and at that path? |
|
It looks like For example, if you run I hope that helps! |
|
awesome! Thanks so much! We're on it. |
|
released 1.0.1 -> https://github.com/infinitered/ignite/releases/tag/1.0.1 |
|
Hi. I updated to the 1.0.1 version, and have rnpm at 1.8.0, but still getting the same error, even sticking to just alphanumeric characters in my project name. The file isn't present, nor are the dirs above it. Thanks. |
|
Hi @amrangaye So, you checked and the file/folders don't exist? There's our problem, so now we need to figure out why. Can you please paste the path it's looking for, and also paste the path to your generated manifest file? You must have a manifest file generated somewhere under the android folder. I think identifying the difference here, we'll have the crux of the problem. |
|
Sure. This is the path/error message:
The android folder doesn't exist at all. Here is a list of dirs actually present in MyApp top level folder: App Tests index.android.js npm-debug.log Thanks. |
|
ok, so something failed inside of generating the react native project at all. So the follow-up steps will fail. Can you provide the contents of Additionally, can you attempt to build a new react-native project and verify that works? |
|
OK so I looked in npm-debug.log, and it seems the initial set of problems were wrong permissions in my ~/.npm dir. I corrected those, and the script makes it a lot further, before failing. However now when I look in the MyApp dir there is no npm-debug.log file - is there another way of checking the error logs? Yes, react-native init MyApp2 works fine. Below is the error log for ignite: |
|
So, that file not existing is key. And the only way that file can not exist is if the The line that runs that inside ignite is this: https://github.com/infinitered/ignite/blob/master/ignite-generator/src/app/index.es#L193 As you can see we have stdio ignore for now, but in your personal |
|
Btw, I am having this problem on OSX El Capitan. I was wondering if this might be an OSX specific problem? |
|
I am using El Capitan Neither /android nor /ios is found. ✔︎ Found react-native Error: ENOENT: no such file or directory, open 'IgniteTest/android/app/src/main/AndroidManifest.xml' |
|
Does the file get created at all? Can you check for it now? Also, can you do a normal |
|
the file does not get created at all |
|
this happens every time? @skellock thoughts on how to best track this down? @VansonLeung - we can help create a branch version perhaps, that would be verbose in each step, rather than swallowing output. Maybe then, it would identify the problem. |
|
make sure you have latest ignite |
|
I can reproduce like this: When it can't find
Should be able to fix this pretty easily. Sorry for the inconvenience. This was a bit goofy to track down. |
|
I was running into this issue on Win10 with Doing this let |
|
@will-hart - That's awesome info! @skellock I'm thinking of building this check into our CLI, thoughts on best way? |
|
hey @GantMan any movement on this? I ran into another wonky issue:
This led me to try to re-scaffold the app and start from scratch but I ran into this issue again. |
|
I created a fresh project about an hour ago. Can you give it a go? I had no issue. make sure you have everything upgraded/updated |
|
Sorry, just going through issues and I've missed this one. @GantMan We could put that check into the cli if you wanted ya. Something like this might do the trick: const cmd = 'npm -s -g ls --depth=0' // lists top level global installed packages
const ohCrap = Shell.exec(cmd, { silent: true }).stdout.indexOf('react-native@') >= 0I mean, we'll only present the same error that |
|
yeah, there's a good bit of checks/balances we can work in to try to help people with borked installs etc. Would be cool to get other team members to maybe PR that. |
|
Upgraded to #276. Thanks all. |
I ran
ignite new appand got the following error:`✔︎ Linking with rnpm
fs.js:584
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT: no such file or directory, open 'dmx-native-mobile-redux/android/app/src/main/AndroidManifest.xml'
at Error (native)
at Object.fs.openSync (fs.js:584:18)
at Object.fs.readFileSync (fs.js:431:33)
at Object.insertInFile (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/utilities.js:21:27)
at performInserts (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/app/index.js:60:13)
at AppGenerator._updateAndroidManifest (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/app/index.js:328:7)
at ChildProcess. (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/app/index.js:378:18)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)`
The text was updated successfully, but these errors were encountered: