-
Notifications
You must be signed in to change notification settings - Fork 24.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task 'installRelease' not found in root project #16854
Comments
$ react-native run-android --variant=release
Scanning folders for symlinks in /media/dj/dev/scan-app/node_modules (16ms)
JS server already running.
Building and installing the app on the device (cd android && ./gradlew installRelease)...
Incremental java compilation is an incubating feature.
FAILURE: Build failed with an exception.
* What went wrong:
Task 'installRelease' not found in root project 'AppName'. Some candidates are: 'uninstallRelease'.
* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 1.283 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 |
i have the same issue |
I was able to run manually: Edit:
|
@BuffMcBigHuge useful, but assembleRelease not the same as installRelease |
As @BuffMcBigHuge said, the problem is the missing singinConfig in gradle files. You have to proper configure it as described in https://facebook.github.io/react-native/docs/signed-apk-android.html and the |
i have also same issue and i tried to install using |
i have the same issue |
In addition to @BuffMcBigHuge , I also made the silly mistake of having my-release-key.keystore in |
Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version? I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer. |
Still Happens on 0.55.2 |
Works for me |
hello people, |
@Manoj002 Have you updated your |
@segheysens , thanks for your response mate |
I'm facing this issue, and I don't have the signing things in the Gradle file because I'm using Fastlane to do that instead. Does that mean I have no option to test it? |
Thank you @mayupat13 for pointing the |
tenha certeza de ter gerado o certificado na pasta android/app/ android/app/buid.gradle
//...` e no android/gradle.properties MYAPP_RELEASE_KEY_ALIAS=my-key-alias MYAPP_RELEASE_STORE_PASSWORD=**** MYAPP_RELEASE_KEY_PASSWORD=**** |
Is this a bug report?
yes
Have you read the Contributing Guidelines?
yes
Environment
Environment:
OS: Linux 4.13
Node: 6.11.4
Yarn: Not Found
npm: 3.10.10
Watchman: 4.7.0
Xcode: N/A
Android Studio: Not Found
Packages: (wanted => installed)
react: ^16.0.0 => 16.0.0
react-native: ^0.50.3 => 0.50.3
Steps to Reproduce
(Write your steps here:)
Expected Behavior
release version of app is installed on connected device like in previous version of react-native
Actual Behavior
Reproducible Demo
follow steps to reproduce
related issue
#16617
The text was updated successfully, but these errors were encountered: