:app:recordFilesBeforeBundleCommandDebug FAILED
See original GitHub issueI get the following error message when running ‘react-native run-android’, and cannot get more detailed information even with --stacktrace, --info or --debug options.
:app:recordFilesBeforeBundleCommandDebug FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:recordFilesBeforeBundleCommandDebug'.
> A problem occurred starting process 'command 'node''
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 3.042 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html
Issue Analytics
- State:
- Created 7 years ago
- Reactions:21
- Comments:40 (14 by maintainers)
Top Results From Across the Web
node.js - :app:recordFilesBeforeBundleCommandDebug FAILED ...
What went wrong: Execution failed for task ':app:recordFilesBeforeBundleCommandDebug'. > Process 'command 'node'' finished with non-zero exit value 1.
Read more >:app:recordFilesBeforeBundleCommandDebug FAILED | Voters ...
:app:recordFilesBeforeBundleCommandDebug FAILED. mkonicek. Moved from https://github.com/facebook/react-native/issues/6875.
Read more >DesktopAppInstaller | Microsoft Store App Failed installing
When this Appinstaller CSP setting is being deployed to NEW enrolled devices you could end up with some weird errors. With the msstore...
Read more >app deploy failed - Google Groups
I discover app engine using the tutorials. I already have two succeed deployed services. They work without any problem(React.js and Hapi.js).
Read more >Windows 10 (1909) Swift 5.2 build error - Compiler
txt" Assertion failed: LastArgWritten == 0, file C:\Users\prafs\swift-base\toolchain\swift\lib\IRGen\GenCall.cpp, line 1868 Stack dump: 0.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve seen this too - similar to @anderson916 in that it’s by no means 100% failing. My workaround is to run ./gradlew --stop (which stops the daemon)
By changing node executable path in build.gradle(app) works for me.