Closed nichiyoshi closed 5 months ago
What was the exit code in the adb shell?
It looks like https://github.com/appium/appium-android-driver/blob/7532ad4d1680b1dd661b55bd3958b6205c47c7f3/lib/commands/intent.js#L155-L166 should handle if the command succeeds by checking the output
I assume it's an issue with the adb itself. Ideally it should return the exit code 0 in case of a successful response. Let me add a a workaround for now :(
I assume it's an issue with the adb itself. Ideally it should return the exit code 0 in case of a successful response. Let me add a a workaround for now :(
Thank you for the quick workaround to fix this! Yes, it seems the issue is of the adb itself. According to logs, I could confirm that it started to happen around the 7th June.
UIA2 driver 3.5.4
has the fix
Issue
I am trying to stop the service of
io.appium.settings/.LocationService
using theexecuteScript("mobile: stopService")
, but it throws WebDriverException as follows.Code
Exception log
This also happens when I execute the same with
executeScript("mobile: shell")
Code
Exception log
If I just run adb command from terminal, it succeeds. -> It turned out it was returning 255, and the message was output to
inputstream
of theProcess
, not theerrorStream