[Android][react-native run-android] app:installDebug error

Question

[Android][react-native run-android] app:installDebug error

muraliv opened this issue 9 years ago · comments

[muralive@AwesomeProject ]$ react-native run-android
Starting JS server...
Building and installing the app on the device (cd android && ./gradlew installDebug)...
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72300Library UP-TO-DATE
:app:prepareComAndroidSupportSupportV42300Library UP-TO-DATE
:app:prepareComFacebookFrescoDrawee061Library UP-TO-DATE
:app:prepareComFacebookFrescoFbcore061Library UP-TO-DATE
:app:prepareComFacebookFrescoFresco061Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipeline061Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipelineOkhttp061Library UP-TO-DATE
:app:prepareComFacebookReactReactNative0110Library UP-TO-DATE
:app:prepareOrgWebkitAndroidJscR174650Library UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:processDebugJavaRes UP-TO-DATE
:app:compileDebugJavaWithJavac UP-TO-DATE
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources UP-TO-DATE
:app:preDexDebug UP-TO-DATE
:app:dexDebug UP-TO-DATE
:app:validateDebugSigning
:app:packageDebug UP-TO-DATE
:app:zipalignDebug UP-TO-DATE
:app:assembleDebug UP-TO-DATE
:app:installDebug FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installDebug'.

com.android.builder.testing.api.DeviceException: com.android.ddmlib.ShellCommandUnresponsiveException
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: 29.7 secs
Could not install the app on the device, see the error above.

syzer commented 8 years ago

👍

Murali Veeraiyan · Answer 1 · Tue Sep 15 2015 16:36:47 GMT+0800 (China Standard Time)

##I'm now getting this error:

:app:installDebug
Skipping device 'emulator-5554' (emulator-5554): Device is OFFLINE.
:app:installDebug FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installDebug'.

com.android.builder.testing.api.DeviceException: No online devices found.
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: 20.503 secs
Could not install the app on the device, see the error above.

Murali Veeraiyan · Answer 2 · Tue Sep 15 2015 17:14:02 GMT+0800 (China Standard Time)

The issue was with the Android Emulator. Changed the AVD settings to enable "Use Host GPU" and the issue was resolved.

Felix Oghină · Answer 3 · Tue Sep 15 2015 18:16:00 GMT+0800 (China Standard Time)

Yes, this is a problem with the Android SDK being super slow sometimes:

ShellCommandUnresponsiveException means installing the APK (simply running adb install) timed out
No online devices found means the emulator went into a bad state and is not responding to any adb commands

Using the host GPU and hardware acceleration (HAXM on OSX / Windows, KVM on Linux) usually helps with this. Or switching to Genymotion.

However, there is nothing we can do about this, since the problem is with the Android tooling. Thus, I'm closing this issue.

leoabacade · Answer 4 · Sat Sep 19 2015 02:42:35 GMT+0800 (China Standard Time)

＠muraliv. you are right, thank you (github needs up-vote function)

Matt Zabriskie · Answer 5 · Fri Oct 09 2015 23:44:03 GMT+0800 (China Standard Time)

@muraliv thanks for the solution!

Ji Gang · Answer 6 · Tue Oct 20 2015 14:48:23 GMT+0800 (China Standard Time)

@muraliv Using the host GPU not work for me. still get

......

:app:validateDebugSigning
:app:packageDebug UP-TO-DATE
:app:zipalignDebug UP-TO-DATE
:app:assembleDebug UP-TO-DATE
:app:installDebug
Skipping device 'emulator-5554' for 'app:debug': Unknown API Level
:app:installDebug FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installDebug'.

Failed to install on any devices.
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: 27.609 secs
Could not install the app on the device, see the error above.

any solutions ?

Eric Chan · Answer 7 · Mon Oct 26 2015 01:18:26 GMT+0800 (China Standard Time)

@jixiaod In case you missed it, you need to start your emulator before running "react-native run-android"

Satyajit Sahoo · Answer 8 · Mon Oct 26 2015 01:26:48 GMT+0800 (China Standard Time)

You can also try Genymotion, it's much faster than the Android Emulator.

Eko Suprapto Wibowo · Answer 9 · Mon Dec 14 2015 22:14:17 GMT+0800 (China Standard Time)

hm, my emulator from genymotion is running, but I also got this error. any suggestion?

puresteelzhang · Answer 10 · Thu Dec 17 2015 14:44:40 GMT+0800 (China Standard Time)

Try:
1、open android Emulator;
2、react-native run-android； error??!! goto 3;
3、adb install app/build/outputs/apk/app-debug.apk；

UK, Jo · Answer 11 · Fri Feb 19 2016 14:27:47 GMT+0800 (China Standard Time)

@jixiaod any update? I got the error you got.

Sebastian Holmqvist · Answer 12 · Sun Feb 28 2016 22:39:48 GMT+0800 (China Standard Time)

@swdevbali Same here. Is Genymotion somehow not targeted?

Sebastian Holmqvist · Answer 13 · Mon Feb 29 2016 19:10:15 GMT+0800 (China Standard Time)

For other coming here, try and downgrade Gradle to version 1.2.3 in your <project-name>/android/build.gradle

#2720

DYQDYQ · Answer 14 · Tue Apr 12 2016 17:43:29 GMT+0800 (China Standard Time)

Execution failed for task ':app:installDebug'.
com.android.ddmlib.ShellCommandUnresponsiveException
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

what should i do

dunhuang · Answer 15 · Mon Apr 25 2016 14:03:07 GMT+0800 (China Standard Time)

@DYQDYQ I faced the same issure, which was sovled by @csholmq's solution.

Wayne Lund · Answer 16 · Tue Jun 07 2016 03:51:22 GMT+0800 (China Standard Time)

I had this issue and it was the wrong "Android SDK Build-tools installed".

Isaac Gongora · Answer 17 · Wed Jun 29 2016 04:49:57 GMT+0800 (China Standard Time)

I can't even start the emulator with avd, did anyone knows why?

Tobias Winkler · Answer 18 · Mon Jul 11 2016 03:37:02 GMT+0800 (China Standard Time)

@wlund-pivotal so simple, but it was exactly my issue, thx! My react-native installation needed 23.0.1, yet I had 24.0.0 installed.

Jax · Answer 19 · Tue Jul 19 2016 00:44:35 GMT+0800 (China Standard Time)

jax$  react-native run-android
Starting JS server...
Building and installing the app on the device (cd android && ./gradlew installDebug...
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

jax$ adb devices
List of devices attached
192.168.56.101:5555 device

how can I fix it , On my computer .
It's ok for react-native run-ios
and it's ok for react-native run-android on my company computer

yybear · Answer 20 · Mon Aug 08 2016 19:03:16 GMT+0800 (China Standard Time)

@verystrongjoe: how did u resolve it?

Emir Marques · Answer 21 · Mon Aug 08 2016 21:44:51 GMT+0800 (China Standard Time)

@yybear look this https://www.youtube.com/watch?v=Ttcsz1h9W9k

BradByte · Answer 22 · Fri Dec 23 2016 05:25:27 GMT+0800 (China Standard Time)

I had this issue when trying to run on my actual device. I was able to resolve it by going into Settings -> Developer Options -> Revoke USB debugging authorization. Then unplug and reattach USB data cable and confirm the authorization.

Nguyễn Minh Đức · Answer 23 · Fri Jan 20 2017 00:21:06 GMT+0800 (China Standard Time)

@muraliv ... how can i change AVD settings to select use host GPU ? . i'm using Android mobile to run react-native ... thanks for your help

Nguyễn Minh Đức · Answer 24 · Fri Jan 20 2017 00:25:33 GMT+0800 (China Standard Time)

@bradbumbalough i saw your instruction, i did it. but it couldn't resolve! ... could you tell me detail to solve this problem! .. thanks you very much

Gerald · Answer 25 · Tue Feb 28 2017 06:49:05 GMT+0800 (China Standard Time)

I had a similar problem. I changed the android gradle plugin version to 2.0.0 in android/build.gradle com.android.tools.build:gradle:2.0.0

And you may need to update the gradle wrapper under "android/gradle/wrapper/gradle-wrapper.properties"
by changing the version to gradle-2.10-all.zip

Bruno Henrique · Answer 26 · Mon May 01 2017 16:59:59 GMT+0800 (China Standard Time)

try to run the cmd as administrator, sometimes it works for me

Erick Chacon · Answer 27 · Fri May 19 2017 01:56:50 GMT+0800 (China Standard Time)

I just ran across the same issue. I was doing everything suggested in the documentation but no luck. What you need to do is open your project through Android Studio, click on the AVD manager icon in the toolbar and run your AVD. Then, run react-native run-android in your terminal.

Kimmer12 · Answer 28 · Tue Jun 06 2017 11:24:15 GMT+0800 (China Standard Time)

My react-native frozen at 97% anyone got the same problem? : mycode:
Starting JS server...
Building and installing the app on the device (cd android && gradlew.bat installDebug)...
Incremental java compilation is an incubating feature.
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72301Library UP-TO-DATE
:app:prepareComAndroidSupportSupportV42301Library UP-TO-DATE
:app:prepareComFacebookFbuiTextlayoutbuilderTextlayoutbuilder100Library UP-TO-DATE
:app:prepareComFacebookFrescoDrawee101Library UP-TO-DATE
:app:prepareComFacebookFrescoFbcore101Library UP-TO-DATE
:app:prepareComFacebookFrescoFresco101Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipeline101Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipelineBase101Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipelineOkhttp3101Library UP-TO-DATE
:app:prepareComFacebookReactReactNative0442Library UP-TO-DATE
:app:prepareComFacebookSoloaderSoloader010Library UP-TO-DATE
:app:prepareOrgWebkitAndroidJscR174650Library UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:mergeDebugShaders UP-TO-DATE
:app:compileDebugShaders UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:bundleDebugJsAndAssets SKIPPED
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
:app:compileDebugJavaWithJavac UP-TO-DATE
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources UP-TO-DATE
:app:transformClassesWithDexForDebug UP-TO-DATE
:app:mergeDebugJniLibFolders UP-TO-DATE
:app:transformNative_libsWithMergeJniLibsForDebug UP-TO-DATE
:app:processDebugJavaRes UP-TO-DATE
:app:transformResourcesWithMergeJavaResForDebug UP-TO-DATE
:app:validateSigningDebug
:app:packageDebug UP-TO-DATE
:app:assembleDebug UP-TO-DATE

Building 97% > :app:installDebug

Korede Bashir · Answer 29 · Wed Aug 02 2017 20:17:12 GMT+0800 (China Standard Time)

@Kimmer12 I'm having the same issue

제이미 · Answer 30 · Mon Aug 07 2017 13:33:22 GMT+0800 (China Standard Time)

My app is already installed on the Android Emulator. So I can see and run them in the emulator.
But it still have same error in the command line

Liron Yahdav · Answer 31 · Thu Aug 17 2017 06:21:21 GMT+0800 (China Standard Time)

I had this issue but was able to resolve by uninstalling my app from the Android emulator and then reinstalling.

Yehuda Zadik · Answer 32 · Fri Sep 22 2017 00:25:04 GMT+0800 (China Standard Time)

The emulator work well on Android Studio but not when I run the command: react-native run-android

If my device is connected to usb _ see the emulator on my phone.

When I run the command without a device connected to usb
I get this error message:

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installDebug'.

com.android.builder.testing.api.DeviceException: No connected devices!

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: 8.179 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

mukeshse · Answer 33 · Tue Sep 26 2017 04:20:08 GMT+0800 (China Standard Time)

No one has the actual solution for this issue... I'v tried all solution above listed but no changes...

Rodolfo Silva · Answer 34 · Sun Oct 01 2017 02:09:48 GMT+0800 (China Standard Time)

I solved same problem on my Ubuntu 16.04 LTS 64bit with installation:
sudo apt-get install lib32z1

Oluwafemi Adekunle · Answer 35 · Tue Nov 14 2017 23:43:33 GMT+0800 (China Standard Time)

I solved same problem by targeting the device id
adb devices to get the device id
react-native run-android --deviceId id

wikieswan · Answer 36 · Wed Nov 15 2017 21:53:50 GMT+0800 (China Standard Time)

@phemonick it works for me

Henry · Answer 37 · Mon Nov 27 2017 18:16:37 GMT+0800 (China Standard Time)

@phemonick thanks it works for me.

Karan Saluja · Answer 38 · Tue Dec 12 2017 17:09:12 GMT+0800 (China Standard Time)

@Kimmer12 I too got the same error. I figured out that I have some error with the adb and that on typing adb devices nothing shows up. Do you know any tweaks to resolve this?

Cody · Answer 39 · Sat Dec 30 2017 18:16:25 GMT+0800 (China Standard Time)

@phemonick it works for me with real android device

Ibrohim Hanafi · Answer 40 · Fri Jan 19 2018 17:16:23 GMT+0800 (China Standard Time)

@phemonick same, it's work for me.
and don't forget to check allow always connect when notification of rsa, so no error again :)

Kate Oliinyk · Answer 41 · Mon Jan 22 2018 23:26:35 GMT+0800 (China Standard Time)

Building 97% > :app:installDebug

@Kimmer12, @bashirk, I had the same problem (waiting for infinity on 97%...), I resolved it by choosing another virtual device preferences in the AVD Manager: it should be "Android 6.0 - API Level 23 - Intel Atom (x86_64)"

Kate Oliinyk · Answer 42 · Mon Jan 22 2018 23:38:42 GMT+0800 (China Standard Time)

on typing adb devices nothing shows up

@Karandeep-Saluja I had this problem too, I guess you have no virtual device installed.
Can you see any devices listed in your AVD Manager?
(You can open the AVD manager using this icon in Android Studio)
If no, you have to create one just clicking on " + Create Virtual Device..."

Karan Saluja · Answer 43 · Tue Jan 23 2018 16:31:44 GMT+0800 (China Standard Time)

@kate-kholyavkina I figured out the solution. The platform-tools installed on my system was faulty. Had to download one from https://developer.android.com/studio/releases/platform-tools.html

Miguel Araya · Answer 44 · Fri Jan 26 2018 17:41:10 GMT+0800 (China Standard Time)

@GerryQuest That worked for me, thank you!

Mustafa K... · Answer 45 · Tue Feb 13 2018 02:23:23 GMT+0800 (China Standard Time)

I had same issue with real device, I changed the cable its fixed...
I have 2 devices for test. (samsung s7 and samsung e7) first cable was working with s7 but the same cable did not work with e7...

Jens Kuhr Jørgensen · Answer 46 · Fri Mar 16 2018 22:23:22 GMT+0800 (China Standard Time)

As @muraliv suggested, I tried changing the graphics, but turns out that is not possible for Google Play enabled devices (which I was using). Created a new AVD without Google Play and it worked - thanks :D

Iliyass Hamza · Answer 47 · Sat Apr 21 2018 01:28:37 GMT+0800 (China Standard Time)

this also happens when you have two adb devices showing up, that's why @phemonick solution works

Prejith Premkumar · Answer 48 · Tue May 29 2018 09:21:58 GMT+0800 (China Standard Time)

I worked around this issue by just restarting the emulator and sometimes, keeping Android Studio open in the background while running npm run android seems to work for me

Erhan BİÇER · Answer 49 · Wed Jul 11 2018 20:16:00 GMT+0800 (China Standard Time)

@phemonick it's worked

Mo Alraddadi · Answer 50 · Wed Jul 11 2018 23:55:31 GMT+0800 (China Standard Time)

Deleting the simulator and creating a new might help