React-native-code-push: Process 'command 'node'' finished with non-zero exit value 1。Error: ENOENT: no such file or directory, open 'E:\Work\PunchCard\code\Daka\android\app\build\intermediates\assets\debug/CodePushHash'

Created on 11 Sep 2018  Â·  9Comments  Â·  Source: microsoft/react-native-code-push

Process 'command 'node'' finished with non-zero exit value 1。

Error: ENOENT: no such file or directory, open 'E:WorkPunchCardcodeDakaandroidappbuildintermediatesassetsdebug/CodePushHash'

Project cannot run。Prompt the above two errors.

ide : android studio;
gradle-wrapper : gradle-4.6-all;
gradle plugin : com.android.tools.build:gradle:3.1.4

android no-response

Most helpful comment

I also experienced the same issue. Workaround is to create the folder manually.

All 9 comments

Hi @yueqch! I've just created a basic RN app with integrated CodePush plugin. Then I've updated gradle-wrapper version to 4.6 and built the app. Result: BUILD SUCCESSFUL. Please take a look at attached demo and change it so that your issue could be reproduced there and share with us. We'll try so figure out what is going wrong.

Note: please execute yarn command in the root of unzipped app before start to build

Hey!
We haven’t heard from you in a while, so I am going to go ahead and close this issue. Should you still have any questions, you can reopen the issue or if you prefer you can create a new one.

I also experienced the same issue. Workaround is to create the folder manually.

We're experiencing this too. Got it after upgrading to Gradle 4.6. Updating code push to latest version didn't help.

Hi @pehagg,

It's actually related to react-native, you can find the answer here.
I hope it will help you. Otherwise feel free to ask any questions!

@yuri-kulikov, thanks a bunch!

For those wondering, the real answer is to upgrade to react-native version 0.57.2 or greater.

Hello guys, i have the same error, i tried what i see here and i have those versions, but still the same
react-native-cli: 2.0.1
react-native: 0.57.3

Any help? Thank you

I also experienced the same issue. Workaround is to create the folder manually.

what folder ???

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ninjz picture ninjz  Â·  4Comments

kevando picture kevando  Â·  4Comments

Fuhrmann picture Fuhrmann  Â·  3Comments

Phredward picture Phredward  Â·  3Comments

jaysig picture jaysig  Â·  3Comments