com.android.ddmlib.InstallException: Failed to establish session react-nativeApplication Installation Failed in Android StudioReact-Native build failed - failed to install allwhy won't run my react-native android app in my custom phone emulatorWhat is the difference between using constructor vs getInitialState in React / React Native?React Native android build failed. SDK location not foundWhat is the difference between React Native and React?Change App Name In React NativeHow to build android apk from my react-native project?react-native run-android stop working by the suddenreact-native :app:installDebug FAILEDApp not starting - React Native (Android)Can't start app using command react-native run-android
How much steel armor can you wear and still be able to swim?
I have found ports on my Samsung smart tv running a display service. What can I do with it?
Would a 7805 5 V regulator drain a 9 V battery?
How do you transpose samples in cents?
Make symbols atomic, without losing their type
What is this airplane that sits in front of Barringer High School in Newark, NJ?
How can a warlock learn from a spellbook?
Story of a Witch Boy
reverse a call to mmap()
Need help understanding the double sharp turn in Chopin's prelude in e minor
S&P 500 Index Value
Unable to import binding 'SforceServiceBinding' with the Summer 19 Tooling API WSDL
Is Newton's third law really correct?
Can the pre-order traversal of two different trees be the same even though they are different?
How do I find which software is doing an SSH connection?
Mapping with iterating uint as identifier - multiple transactions in the same block
Understanding “en comprend”
"Prove that ∂A is closed given ∂A = Cl(A) − Int(A)"
In Street Fighter, what does the M stand for in M Bison?
Umlaut character order when sorting
How does Frenetic Sliver interact with the Unearth from Dregscape Sliver?
Why isn't my calculation that we should be able to see the sun well beyond the observable universe valid?
Is there any possible way to get these hearts as Adult Link?
Are there any individual aliens that have gained superpowers in the Marvel universe?
com.android.ddmlib.InstallException: Failed to establish session react-native
Application Installation Failed in Android StudioReact-Native build failed - failed to install allwhy won't run my react-native android app in my custom phone emulatorWhat is the difference between using constructor vs getInitialState in React / React Native?React Native android build failed. SDK location not foundWhat is the difference between React Native and React?Change App Name In React NativeHow to build android apk from my react-native project?react-native run-android stop working by the suddenreact-native :app:installDebug FAILEDApp not starting - React Native (Android)Can't start app using command react-native run-android
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am trying to run react-native android app in my nexus5 emulator
adb devices
List of devices attached
emulator-5554 device
started packager react-native start
running app - react-native run-android
Installing APK 'app-debug.apk' on 'reactnative(AVD) - 6.0'
Unable to install examples/android/app/build/outputs/apk/app-debug.apk
com.android.ddmlib.InstallException: Failed to establish session
at com.android.ddmlib.Device.installPackages(Device.java:894)
at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:113)
at com.android.builder.testing.ConnectedDevice$installPackages$0.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.groovy:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226)
android react-native
add a comment |
I am trying to run react-native android app in my nexus5 emulator
adb devices
List of devices attached
emulator-5554 device
started packager react-native start
running app - react-native run-android
Installing APK 'app-debug.apk' on 'reactnative(AVD) - 6.0'
Unable to install examples/android/app/build/outputs/apk/app-debug.apk
com.android.ddmlib.InstallException: Failed to establish session
at com.android.ddmlib.Device.installPackages(Device.java:894)
at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:113)
at com.android.builder.testing.ConnectedDevice$installPackages$0.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.groovy:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226)
android react-native
3
Note thatreact-native run-android
also starts the packager, no need to start it manually.
– Martin Konicek
Sep 15 '15 at 20:46
3
I resolved this issue, by simply creating a new android virtual device. Not exactly sure what was causing it.
– Magnuss
Sep 16 '15 at 13:24
add a comment |
I am trying to run react-native android app in my nexus5 emulator
adb devices
List of devices attached
emulator-5554 device
started packager react-native start
running app - react-native run-android
Installing APK 'app-debug.apk' on 'reactnative(AVD) - 6.0'
Unable to install examples/android/app/build/outputs/apk/app-debug.apk
com.android.ddmlib.InstallException: Failed to establish session
at com.android.ddmlib.Device.installPackages(Device.java:894)
at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:113)
at com.android.builder.testing.ConnectedDevice$installPackages$0.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.groovy:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226)
android react-native
I am trying to run react-native android app in my nexus5 emulator
adb devices
List of devices attached
emulator-5554 device
started packager react-native start
running app - react-native run-android
Installing APK 'app-debug.apk' on 'reactnative(AVD) - 6.0'
Unable to install examples/android/app/build/outputs/apk/app-debug.apk
com.android.ddmlib.InstallException: Failed to establish session
at com.android.ddmlib.Device.installPackages(Device.java:894)
at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:113)
at com.android.builder.testing.ConnectedDevice$installPackages$0.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.groovy:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226)
android react-native
android react-native
asked Sep 15 '15 at 4:32
invariantinvariant
6,59163752
6,59163752
3
Note thatreact-native run-android
also starts the packager, no need to start it manually.
– Martin Konicek
Sep 15 '15 at 20:46
3
I resolved this issue, by simply creating a new android virtual device. Not exactly sure what was causing it.
– Magnuss
Sep 16 '15 at 13:24
add a comment |
3
Note thatreact-native run-android
also starts the packager, no need to start it manually.
– Martin Konicek
Sep 15 '15 at 20:46
3
I resolved this issue, by simply creating a new android virtual device. Not exactly sure what was causing it.
– Magnuss
Sep 16 '15 at 13:24
3
3
Note that
react-native run-android
also starts the packager, no need to start it manually.– Martin Konicek
Sep 15 '15 at 20:46
Note that
react-native run-android
also starts the packager, no need to start it manually.– Martin Konicek
Sep 15 '15 at 20:46
3
3
I resolved this issue, by simply creating a new android virtual device. Not exactly sure what was causing it.
– Magnuss
Sep 16 '15 at 13:24
I resolved this issue, by simply creating a new android virtual device. Not exactly sure what was causing it.
– Magnuss
Sep 16 '15 at 13:24
add a comment |
12 Answers
12
active
oldest
votes
For Mi devices
for those who suffer from this, try what lironess mentions in a Github Comment
enable developer mode - In your phone, go to Settings, About phone and click on MIUI version 7 times. You’ll see a pop up which
says you are a developer now.
- Go back to Settings, Additional settings, Developer options and enable USB Debugging.
Connect your phone to your PC/Mac and on the phone authorize your computer
- go back to Developer options, scroll down to find Turn on MIUI optimization and disable it. Your phone will be rebooted
- Try it now :)
add a comment |
Try : react-native run-android --deviceId YOUR_ID
.
add a comment |
adb is known to be flaky. Try:
- Restarting adb with
$ adb kill-server
- Restarting the emulator
- Using Genymotion instead of stock Google emulator.
1
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
1
This error is happen to me usingGenymotion
– jose920405
Aug 2 '17 at 13:45
add a comment |
For your AVD emulator settings, try to make sure the "Use Host GPU" setting is checked, and relaunch the emulator and try again.
3
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
add a comment |
In my case, I have to run this command in
/sdklocation/platform-tools/
adb kill-server
then run again and watch for install request on the phone.
hope this help some one
add a comment |
For those like me having this issue in the emulator, one more tip: try to free up the available storage space in the emulator. That worked for me.
So many test apps and previous developed apps installed XD
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
add a comment |
If you had already installed app on device go delete it. It's work for me
add a comment |
If your device or emulator have an application having same name with the application you are building. Just remove the old one. It will resolve the issue.
add a comment |
Even i had the same problem,but restarting the genymotion and running the "react-native run-android" again worked for me.
Ensure genymotion is running before running the above command.
add a comment |
Probable Cause
I faced this issue recently , I had first developed an app called
'myApp' in CordovaJS where the app domain was com.myapp and had it
installed (this was months before I got into react ). Then when I
switched to react-native I did an app with a domain com.myapp and ran
into the same problem you are in.
So I figured out that there was conflicts when it came to domain and source .
Solution :
Uninstall the app that has a similar domain as the one that you are
installing eg com.example , then reboot your phone .
It worked for me , I hope it works for you too.
add a comment |
01 - Uninstall the app installed in device
03- then run
- adb kill-server
02 -Then run again
- react-native run-android
add a comment |
This issue happens to occur in Xiomi devices. In developers option, you don't have to disable MIUI optimization(disabling this won't sync your accounts) instead, enable 'USB debugging' option along with 'Install via USB' and 'USB debugging(Security settings)'.
This will solve the issue :)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32577761%2fcom-android-ddmlib-installexception-failed-to-establish-session-react-native%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
12 Answers
12
active
oldest
votes
12 Answers
12
active
oldest
votes
active
oldest
votes
active
oldest
votes
For Mi devices
for those who suffer from this, try what lironess mentions in a Github Comment
enable developer mode - In your phone, go to Settings, About phone and click on MIUI version 7 times. You’ll see a pop up which
says you are a developer now.
- Go back to Settings, Additional settings, Developer options and enable USB Debugging.
Connect your phone to your PC/Mac and on the phone authorize your computer
- go back to Developer options, scroll down to find Turn on MIUI optimization and disable it. Your phone will be rebooted
- Try it now :)
add a comment |
For Mi devices
for those who suffer from this, try what lironess mentions in a Github Comment
enable developer mode - In your phone, go to Settings, About phone and click on MIUI version 7 times. You’ll see a pop up which
says you are a developer now.
- Go back to Settings, Additional settings, Developer options and enable USB Debugging.
Connect your phone to your PC/Mac and on the phone authorize your computer
- go back to Developer options, scroll down to find Turn on MIUI optimization and disable it. Your phone will be rebooted
- Try it now :)
add a comment |
For Mi devices
for those who suffer from this, try what lironess mentions in a Github Comment
enable developer mode - In your phone, go to Settings, About phone and click on MIUI version 7 times. You’ll see a pop up which
says you are a developer now.
- Go back to Settings, Additional settings, Developer options and enable USB Debugging.
Connect your phone to your PC/Mac and on the phone authorize your computer
- go back to Developer options, scroll down to find Turn on MIUI optimization and disable it. Your phone will be rebooted
- Try it now :)
For Mi devices
for those who suffer from this, try what lironess mentions in a Github Comment
enable developer mode - In your phone, go to Settings, About phone and click on MIUI version 7 times. You’ll see a pop up which
says you are a developer now.
- Go back to Settings, Additional settings, Developer options and enable USB Debugging.
Connect your phone to your PC/Mac and on the phone authorize your computer
- go back to Developer options, scroll down to find Turn on MIUI optimization and disable it. Your phone will be rebooted
- Try it now :)
edited Jun 8 at 1:35
Bhargav Rao♦
31.8k2193115
31.8k2193115
answered Sep 10 '16 at 11:29
shrestha rohitshrestha rohit
2,6511918
2,6511918
add a comment |
add a comment |
Try : react-native run-android --deviceId YOUR_ID
.
add a comment |
Try : react-native run-android --deviceId YOUR_ID
.
add a comment |
Try : react-native run-android --deviceId YOUR_ID
.
Try : react-native run-android --deviceId YOUR_ID
.
answered Aug 13 '17 at 22:26
Badis MerabetBadis Merabet
3,1462136
3,1462136
add a comment |
add a comment |
adb is known to be flaky. Try:
- Restarting adb with
$ adb kill-server
- Restarting the emulator
- Using Genymotion instead of stock Google emulator.
1
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
1
This error is happen to me usingGenymotion
– jose920405
Aug 2 '17 at 13:45
add a comment |
adb is known to be flaky. Try:
- Restarting adb with
$ adb kill-server
- Restarting the emulator
- Using Genymotion instead of stock Google emulator.
1
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
1
This error is happen to me usingGenymotion
– jose920405
Aug 2 '17 at 13:45
add a comment |
adb is known to be flaky. Try:
- Restarting adb with
$ adb kill-server
- Restarting the emulator
- Using Genymotion instead of stock Google emulator.
adb is known to be flaky. Try:
- Restarting adb with
$ adb kill-server
- Restarting the emulator
- Using Genymotion instead of stock Google emulator.
edited Sep 16 '15 at 0:34
answered Sep 15 '15 at 20:48
Martin KonicekMartin Konicek
25k156782
25k156782
1
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
1
This error is happen to me usingGenymotion
– jose920405
Aug 2 '17 at 13:45
add a comment |
1
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
1
This error is happen to me usingGenymotion
– jose920405
Aug 2 '17 at 13:45
1
1
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
yeah i gave up on google emulator , its working fine on genymotion though :)
– invariant
Sep 15 '15 at 22:03
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
Cool! Glad it worked.
– Martin Konicek
Sep 16 '15 at 0:34
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
@invariant Does Genymotion support google play services
– Utsav Gupta
Jul 2 '16 at 7:42
1
1
This error is happen to me using
Genymotion
– jose920405
Aug 2 '17 at 13:45
This error is happen to me using
Genymotion
– jose920405
Aug 2 '17 at 13:45
add a comment |
For your AVD emulator settings, try to make sure the "Use Host GPU" setting is checked, and relaunch the emulator and try again.
3
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
add a comment |
For your AVD emulator settings, try to make sure the "Use Host GPU" setting is checked, and relaunch the emulator and try again.
3
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
add a comment |
For your AVD emulator settings, try to make sure the "Use Host GPU" setting is checked, and relaunch the emulator and try again.
For your AVD emulator settings, try to make sure the "Use Host GPU" setting is checked, and relaunch the emulator and try again.
answered Oct 21 '15 at 23:14
Edward TEdward T
651710
651710
3
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
add a comment |
3
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
3
3
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
For me - I was able to get this working without Host GPU (in fact I had to turn on software rendering to get the emulator to even start, likely due to my old video card/driver). I too was getting this error but it turns out I wasn't being patient enough - it took forever for the emulator to finish coming up, once it did (ie phone showed its 'desktop') then react-native was able to install the build
– bitcoder
Aug 9 '16 at 18:45
add a comment |
In my case, I have to run this command in
/sdklocation/platform-tools/
adb kill-server
then run again and watch for install request on the phone.
hope this help some one
add a comment |
In my case, I have to run this command in
/sdklocation/platform-tools/
adb kill-server
then run again and watch for install request on the phone.
hope this help some one
add a comment |
In my case, I have to run this command in
/sdklocation/platform-tools/
adb kill-server
then run again and watch for install request on the phone.
hope this help some one
In my case, I have to run this command in
/sdklocation/platform-tools/
adb kill-server
then run again and watch for install request on the phone.
hope this help some one
edited Aug 1 '17 at 3:35
answered Mar 6 '17 at 7:41
maxmax
2,36082651
2,36082651
add a comment |
add a comment |
For those like me having this issue in the emulator, one more tip: try to free up the available storage space in the emulator. That worked for me.
So many test apps and previous developed apps installed XD
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
add a comment |
For those like me having this issue in the emulator, one more tip: try to free up the available storage space in the emulator. That worked for me.
So many test apps and previous developed apps installed XD
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
add a comment |
For those like me having this issue in the emulator, one more tip: try to free up the available storage space in the emulator. That worked for me.
So many test apps and previous developed apps installed XD
For those like me having this issue in the emulator, one more tip: try to free up the available storage space in the emulator. That worked for me.
So many test apps and previous developed apps installed XD
answered Aug 31 '17 at 11:48
CosmitarCosmitar
462513
462513
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
add a comment |
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Yes, the insufficient storage was causing this error for me also. Editing the emulator and adding more memory solved the issue.
– vovahost
May 24 '18 at 12:51
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
Same here, just storage on a real device was full in my case.
– Andru
Oct 16 '18 at 15:19
add a comment |
If you had already installed app on device go delete it. It's work for me
add a comment |
If you had already installed app on device go delete it. It's work for me
add a comment |
If you had already installed app on device go delete it. It's work for me
If you had already installed app on device go delete it. It's work for me
answered Feb 14 '17 at 11:55
Khalid AhmadaKhalid Ahmada
119111
119111
add a comment |
add a comment |
If your device or emulator have an application having same name with the application you are building. Just remove the old one. It will resolve the issue.
add a comment |
If your device or emulator have an application having same name with the application you are building. Just remove the old one. It will resolve the issue.
add a comment |
If your device or emulator have an application having same name with the application you are building. Just remove the old one. It will resolve the issue.
If your device or emulator have an application having same name with the application you are building. Just remove the old one. It will resolve the issue.
answered Mar 25 at 6:04
CodemakerCodemaker
1,062820
1,062820
add a comment |
add a comment |
Even i had the same problem,but restarting the genymotion and running the "react-native run-android" again worked for me.
Ensure genymotion is running before running the above command.
add a comment |
Even i had the same problem,but restarting the genymotion and running the "react-native run-android" again worked for me.
Ensure genymotion is running before running the above command.
add a comment |
Even i had the same problem,but restarting the genymotion and running the "react-native run-android" again worked for me.
Ensure genymotion is running before running the above command.
Even i had the same problem,but restarting the genymotion and running the "react-native run-android" again worked for me.
Ensure genymotion is running before running the above command.
answered Aug 22 '17 at 7:36
Thanmai CThanmai C
24639
24639
add a comment |
add a comment |
Probable Cause
I faced this issue recently , I had first developed an app called
'myApp' in CordovaJS where the app domain was com.myapp and had it
installed (this was months before I got into react ). Then when I
switched to react-native I did an app with a domain com.myapp and ran
into the same problem you are in.
So I figured out that there was conflicts when it came to domain and source .
Solution :
Uninstall the app that has a similar domain as the one that you are
installing eg com.example , then reboot your phone .
It worked for me , I hope it works for you too.
add a comment |
Probable Cause
I faced this issue recently , I had first developed an app called
'myApp' in CordovaJS where the app domain was com.myapp and had it
installed (this was months before I got into react ). Then when I
switched to react-native I did an app with a domain com.myapp and ran
into the same problem you are in.
So I figured out that there was conflicts when it came to domain and source .
Solution :
Uninstall the app that has a similar domain as the one that you are
installing eg com.example , then reboot your phone .
It worked for me , I hope it works for you too.
add a comment |
Probable Cause
I faced this issue recently , I had first developed an app called
'myApp' in CordovaJS where the app domain was com.myapp and had it
installed (this was months before I got into react ). Then when I
switched to react-native I did an app with a domain com.myapp and ran
into the same problem you are in.
So I figured out that there was conflicts when it came to domain and source .
Solution :
Uninstall the app that has a similar domain as the one that you are
installing eg com.example , then reboot your phone .
It worked for me , I hope it works for you too.
Probable Cause
I faced this issue recently , I had first developed an app called
'myApp' in CordovaJS where the app domain was com.myapp and had it
installed (this was months before I got into react ). Then when I
switched to react-native I did an app with a domain com.myapp and ran
into the same problem you are in.
So I figured out that there was conflicts when it came to domain and source .
Solution :
Uninstall the app that has a similar domain as the one that you are
installing eg com.example , then reboot your phone .
It worked for me , I hope it works for you too.
answered Feb 26 '18 at 14:54
Daggie BlanqxDaggie Blanqx
455613
455613
add a comment |
add a comment |
01 - Uninstall the app installed in device
03- then run
- adb kill-server
02 -Then run again
- react-native run-android
add a comment |
01 - Uninstall the app installed in device
03- then run
- adb kill-server
02 -Then run again
- react-native run-android
add a comment |
01 - Uninstall the app installed in device
03- then run
- adb kill-server
02 -Then run again
- react-native run-android
01 - Uninstall the app installed in device
03- then run
- adb kill-server
02 -Then run again
- react-native run-android
answered Sep 11 '18 at 4:17
Rumesh MadushankaRumesh Madushanka
10524
10524
add a comment |
add a comment |
This issue happens to occur in Xiomi devices. In developers option, you don't have to disable MIUI optimization(disabling this won't sync your accounts) instead, enable 'USB debugging' option along with 'Install via USB' and 'USB debugging(Security settings)'.
This will solve the issue :)
add a comment |
This issue happens to occur in Xiomi devices. In developers option, you don't have to disable MIUI optimization(disabling this won't sync your accounts) instead, enable 'USB debugging' option along with 'Install via USB' and 'USB debugging(Security settings)'.
This will solve the issue :)
add a comment |
This issue happens to occur in Xiomi devices. In developers option, you don't have to disable MIUI optimization(disabling this won't sync your accounts) instead, enable 'USB debugging' option along with 'Install via USB' and 'USB debugging(Security settings)'.
This will solve the issue :)
This issue happens to occur in Xiomi devices. In developers option, you don't have to disable MIUI optimization(disabling this won't sync your accounts) instead, enable 'USB debugging' option along with 'Install via USB' and 'USB debugging(Security settings)'.
This will solve the issue :)
answered Mar 30 at 7:18
Aishwarya MundadaAishwarya Mundada
13
13
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32577761%2fcom-android-ddmlib-installexception-failed-to-establish-session-react-native%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Note that
react-native run-android
also starts the packager, no need to start it manually.– Martin Konicek
Sep 15 '15 at 20:46
3
I resolved this issue, by simply creating a new android virtual device. Not exactly sure what was causing it.
– Magnuss
Sep 16 '15 at 13:24