Skip to content
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

react-native run-android shows BUILD SUCCESSFUL but exits the process #26636

Closed
KevBeltrao opened this issue Sep 29, 2019 · 11 comments
Closed

react-native run-android shows BUILD SUCCESSFUL but exits the process #26636

KevBeltrao opened this issue Sep 29, 2019 · 11 comments
Labels
Bug Platform: Android Android applications. Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@KevBeltrao
Copy link

React Native version: 0.61.1
Operational System: Ubuntu 18.04

What I did

  1. Followed the documentation steps to get started with React Native CLI Quickstart
  2. Added my user tu the group of the /dev/kvm
  3. Deleted the node_modules and ran sudo npm install.
  4. Ran sudo chmod -R 777 ... to the project folder (AwesomeProject) and the node_modules.

Problem

I could fix a bunch of problems looking up online but I still can't run the project. I am opening my AVD and running the command react-native run-android, it seems to go right but exits the process and my project doesn't run.

Here's what I get:
(terminal view)

kbmelo@kbmelo:~/Documents/AwesomeProject$ react-native run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 863 file(s) to forward-jetify. Using 8 workers...
info Starting JS server...
info Installing the app...

> Task :app:installDebug
06:37:50 V/ddms: execute: running am get-config
06:37:50 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1
06:37:50 V/ddms: execute: returning
Installing APK 'app-debug.apk' on 'Galaxy_Nexus_API_28(AVD) - 9' for app:debug
06:37:50 D/app-debug.apk: Uploading app-debug.apk onto device 'emulator-5554'
06:37:50 D/Device: Uploading file onto device 'emulator-5554'
06:37:50 D/ddms: Reading file permision of /home/kbmelo/Documents/AwesomeProject/android/app/build/outputs/apk/debug/app-debug.apk as: rwxrwxrwx
06:37:50 V/ddms: execute: running pm install -r -t "/data/local/tmp/app-debug.apk"
06:37:51 V/ddms: execute 'pm install -r -t "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
06:37:51 V/ddms: execute: returning
06:37:51 V/ddms: execute: running rm "/data/local/tmp/app-debug.apk"
06:37:51 V/ddms: execute 'rm "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
06:37:51 V/ddms: execute: returning
Installed on 1 device.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.5/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 3s
27 actionable tasks: 2 executed, 25 up-to-date
info Connecting to the development server...
info Starting the app on "emulator-5554"...
Starting: Intent { cmp=com.awesomeproject/.MainActivity }
@KevBeltrao KevBeltrao added the Bug label Sep 29, 2019
@react-native-bot react-native-bot added the Platform: Android Android applications. label Sep 29, 2019
@eggybot
Copy link

eggybot commented Sep 29, 2019

I think you need to reinstall all setup again without sudo. RN suggest that you should not use sudo when installing and executing run builds. This will have conflict with permissions.

@ismetsezer
Copy link

Did you check does app refreshed after build successful by opening manually. I got it , your app didn't started after build process but is app refreshed ? Check it please .

@Navidhp
Copy link

Navidhp commented Sep 30, 2019

@kbmelo the new version in react native is not start node server and run your project after success build you must run node server with react-native start and open your project

@DPflasterer
Copy link

I'm also seeing this after upgrading to 0.61.1 (from 0.59.9.) It works fine when I run react-native start and react-native android in their own consoles. Before the upgrade I only had to run react-native android.

Is this an issue with this release or a configuration issue?

@qingjiaowochengzd
Copy link

+1

@JslinSir
Copy link

I also encountered the same problem, my solution is to clean the mobile storage space.(Also is the space to install the software should be greater than 200 M On my phone ---

@pam3ec555
Copy link

Do you have any other terminal windows after react-native run-android? If you do, let me see the content of a window of a terminal

@Aboude-Adra
Copy link

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.

I'm also getting the same above error only when using VS App Center to build, although I can locally build and run normally using react-native run-android

@Aboude-Adra
Copy link

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.

I'm also getting the same above error only when using VS App Center to build, although I can locally build and run normally using react-native run-android

Turned out my debug.keystore was missing from my branch, related to this issue > #25629

@stale
Copy link

stale bot commented May 30, 2020

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label May 30, 2020
@stale
Copy link

stale bot commented Jun 6, 2020

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Jun 6, 2020
@facebook facebook locked as resolved and limited conversation to collaborators Jun 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Platform: Android Android applications. Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

10 participants