I am failed to push "AppiumBootstrap.jar" to my real phone huawei honor6

hello to whom will see my issue, I will be very thanksfull for your reply to my issue:
1-I have successfully setup my win10_64 and installed the appium, java, android and etc.
2-when I run my testing project in eclipse, I see from appium that the “AppiumBootstrap.jar” failed to push my real Android phone–huawei honor6(4.4.2).
here is the log:

info: → POST /wd/hub/session {“desiredCapabilities”:{“appPackage”:“com.latvisoft.jabraassist”,“appActivity”:“com.jabra.assist.ui.start.SplashActivity”,“platformVersion”:“5.0.1”,“automationName”:“UiAutomator”,“platformName”:“Android”,“udid”:“022SSE146M005259”,“deviceName”:“Android”}}
info: Client User-Agent string: Apache-HttpClient/4.5.1 (Java/1.8.0_73)
info: [debug] Didn’t get app but did get Android package, will attempt to launch it on the device
info: [debug] Creating new appium session 0a1b3d36-5a8e-4b49-a8b6-dceed8ca3428
info: Starting android appium
info: [debug] Getting Java version
info: Java version is: 1.8.0_73
info: [debug] Checking whether adb is present
info: [debug] Using adb from D:\AndroidSDK\platform-tools\adb.exe
warn: No app capability, can’t parse package/activity
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Not checking whether app is present since we are assuming it’s already on the device
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe devices
info: [debug] 1 device(s) connected
info: Found device 022SSE146M005259
info: [debug] Setting device id to 022SSE146M005259
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 wait-for-device
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Getting device API level
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 19
info: Device API level is: 19
info: [debug] Extracting strings for language: default
info: [debug] Apk doesn’t exist locally
info: [debug] Could not get strings, but it looks like we had an old strings file anyway, so ignoring
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 shell “rm -rf /data/local/tmp/strings.json”
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Skipping install since we launched with a package instead of an app path
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
info: [debug] Logcat terminated with code 0, signal null
info: [debug] Stopping logcat capture
info: [debug] Logcat already stopped
info: [debug] Sent shutdown command, waiting for UiAutomator to stop…
warn: UiAutomator did not shut down fast enough, calling it gone
info: [debug] Cleaning up android objects
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Command failed: C:\Windows\system32\cmd.exe /s /c “D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/”
failed to read ID_DONE response for ‘C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar’: Invalid argument
9 KB/s (48866 bytes in 5.081s)

info: [debug] Error: Command failed: C:\Windows\system32\cmd.exe /s /c “D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/”
failed to read ID_DONE response for ‘C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar’: Invalid argument
9 KB/s (48866 bytes in 5.081s)

at ChildProcess.exithandler (child_process.js:751:12)
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1016:16)
at Process.ChildProcess._handle.onexit (child_process.js:1088:5)

info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Command failed: C:\Windows\system32\cmd.exe /s /c "D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push "C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/"\nfailed to read ID_DONE response for ‘C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar’: Invalid argument\r\n9 KB/s (48866 bytes in 5.081s)\r\n)”,“killed”:false,“code”:1,“signal”:null,“cmd”:“C:\Windows\system32\cmd.exe /s /c "D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push "C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/"”,“origValue”:“Command failed: C:\Windows\system32\cmd.exe /s /c "D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push "C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/"\nfailed to read ID_DONE response for ‘C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar’: Invalid argument\r\n9 KB/s (48866 bytes in 5.081s)\r\n”},“sessionId”:null}
info: ← POST /wd/hub/session 500 13040.579 ms - 1344
honor6.txt (5.7 KB)

To troubleshoot this you should give the command that is failing (above) from the command line. You are looking for any logging/errors that are not being surfaced in Appium. You may need to make some permissions adjustments to ‘/data/local/tmp/’.

Hi, Dear Wreed, thanks so much for you reply.
here is the command failed:
info: [debug] executing cmd: D:\AndroidSDK\platform-tools\adb.exe -s 022SSE146M005259 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
I also tried another phone LG neuxs5 which does not have this issue and success on this command.

one more thing I need to highlight, the most strange behavior is that I can make it work on my laptop thinkpad T430 but failed on my PC with my huawei honor6(4.4.2).

Hi @sean_peng!

I think what @wreed is suggesting is that you should run that command by itself, without having Appium run it during Appium’s set-up phase. Copy that command, open a command prompt on your Windows machine, paste the command to the command line, press enter to see what happens with your Huawei phone. Does the command succeed or fail?

hi Dear afwang,
thanks so much for you valuable comments.
I have tried from command line ffrom pc singlely.
but seems failed the same.

Most excellent! So now your job is to figure out the difference between these two machines. If you would post logs of the failures as well as the success I might be able to help. However, the burden is upon you to figure out why you have one machine that is not working. It’s obvious that Appium itself is working.

nexus5.txt (12.9 KB)

Hi Dear wreed
here is the log of nexus5 with success on the PC.
the neuxs5 is working fine on both my PC and laptop.
but the honor6 is working on my laptop but not the PC.
here I upload the log of the nexus5(5.0.1).

Ok, so I’m just going to review here:

  1. with the nexus5, appium is working fine on both machines
  2. with the honor6, appium is working on the laptop but not the PC

So what’s the difference? Are they running the same OS? Do they have the same version of Appium? If you really want to troubleshoot this, you need to answer those questions. Something is different, and by figuring that out you’ll be able to fix the problem.

Another thing to look at is Eclipse. Are these the same versions of Eclipse? Are they set up the same way? Is the code you are running on each machine the same? There are a lot of variables here that people reading this cannot guess at.

You’ve got it working very well on one machine. Try to duplicate the same setup on the other.

Hi Dear Wreed
thanks so much for you consistent support on me.
I finally could make this honor6 working on my PC.
I change the front USB port to the back USB port of my PC then everythings goes well.
but the only strange issue is that my nexus5 is working fine with the front USB port any way.
but no need to worry about that any, I need to struggle how to implement the test for the app on my phone.
thanks again for your support on me these days, Dear Wreed!!!

BR
Sean Peng

1 Like