Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Task 'installDebug' not found in root project ' '.
See original GitHub issueDescription
Hi, I am new to react/react-native and I have a problem that I’ve been trying to fix for a week. I’ve created a react native app with the react-native-cli with the cmd: react-native init myApp. After my app gets created automatically. I run this command: react-native run-android and I get this error:
so then to try and fix that I go into the android directory and use the cmd: gradlew :app:installDebug and it builds successfully:
then I go back into my project directory and run-android again. I expected that this app would run on my android virtual device but I get the same error:
So at this point I know there is something seriously wrong so I go back into the android directory and type in this cmd: gradlew build and this fails at the bundleReleaseJsAndAssets:
I don’t know if this is the problem but something is not working correctly. Like I said I’ve been trying to fix this for a week and looked at several forums to fix this. I found a issue that has the same build errors as me except this was 2 years ago and he is building the assembleRelease for android with a different version of react: #4124 .
Reproduction Steps and Sample Code
If you can get my React-Native app running on your Windows or even your mac let me know what you did. Here is the link to my frustrating app: https://github.com/CoLagon/React-Native-myApp
Additional Information
- React Native version: 0.42.3
- Platform: Android
- Development Operating System: Windows 10
- Dev tools: [Android SDK 23.0.1 - 23.0.3]
Issue Analytics
- State:
- Created 6 years ago
- Comments:11
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Air-Miha
HEYYYYYYYYYYYYY!!! I FIXXED IT!!! OMG. I’m so happy. Thank you so much you inspired me to think and fix the problem. so when you said that it might be my environment, I scratched my head was thinking about my environment variables and things I did to my computer. So about a month ago I went into my registry editor (regedit) and made a new string value in
HKEY_CURRENT_USER\Software\Microsoft\Command Processorcalled Autorun so when I open up my command prompt my cmd path would be set to my hard drive (C:). So I removed that and it work! That what was wrong with my computer that entire time. so I guess I learned today to never mess with the regedit. I seriously didn’t think that was the problem but it was thank god I removed that.@colelogan thank you a lot. work it. i remove autorun from registry and work!