samsung / appium-tizen-driver Goto Github PK

The problem

The commands tizen driver offers us do not work for TV devices. Every connection to real tizen TV device is followed by "Getting install status for 'appPackage'" command. This and other available commands are executed over "sdb shell".
"sdb shell" is not supported neither by TV emulators nor by real TV devices, unless real TV device has "debug firmware installed".
According to what I see from Appium server log, tizen driver executes 'sdb shell' scripts directly against device and throws "sdb shell ... exited with code 1'; Stderr: 'closed';".
It will never work since it is blocked by TV firmware. The only way it could be done is over socket connection, I see some JS code related to socket connection but most likely the requests to the device are not going through the socket.

Environment

• Appium version (or git revision) that exhibits the issue: 1.9.0
• Last Appium version that did not exhibit the issue (if applicable): -
• Desktop OS/version used to run Appium: Windows 10
• Node.js version (unless using Appium.app|exe): 5.6.0
• Mobile platform/version under test: Tizen 3.0, same behavior for Tizen 2.3 and Tizen 4.0
• Real device or emulator/simulator: Real Tizen TV Devices and Tizen TV emulators
• Appium CLI or Appium.app|exe:

Link to Appium logs

GIST

Code To Reproduce Issue [ Good To Have ]

To repro the issue it is enough to start Appium server 1.9.0 with capabilities
{
"appPackage": "sample",
"deviceName": "Tizen",
"platformName": "Tizen"
}

Hello!
I tried to run the Appium test on my Gear S3, but I got an issue. Every time I got an error: _Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: Tizen bootstrap socket crashed: Error: This socket has been ended by the other party_
Also, I tried to use a wearable emulator but got the same error. Could you please help with this issue or to advice what I have to do to avoid it?

Test code
desiredCapabilities.setCapability("appPackage", "org.tizen.w-contacts.app-control"); desiredCapabilities.setCapability("newCommandTimeout", "600"); desiredCapabilities.setCapability("deviceName", "Tizen"); desiredCapabilities.setCapability("platformName", "Tizen"); RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4723/wd/hub"), desiredCapabilities); driver.navigate().back();

I see port forwarding using 8888 port but nothing is started on a device with this value...
Also, I see that uiautomator use dynamic ports on a device to listen something:
netstat -anp | grep uiau

Logs
appium-server-logs.txt

Do you folks mind releasing a new version of appium-sdb. It still uses an old version of lodash which has a vulnerability.

(related to appium/appium#12441)

See output of npm audit below. The package lodash should be updated to >= 4.17.5. See advisory: https://nodesecurity.io/advisories/577.

$ npm audit

                       === npm audit security report ===

┌──────────────────────────────────────────────────────────────────────────────┐
│                                Manual Review                                 │
│            Some vulnerabilities require your attention to resolve            │
│                                                                              │
│         Visit https://go.npm.me/audit-guide for additional guidance          │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low           │ Prototype Pollution                                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ lodash                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=4.17.5                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ appium [dev]                                                 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ appium > appium-tizen-driver > appium-sdb > lodash           │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://nodesecurity.io/advisories/577                       │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low           │ Prototype Pollution                                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ lodash                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=4.17.5                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ appium [dev]                                                 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ appium > appium-tizen-driver > lodash                        │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://nodesecurity.io/advisories/577                       │
└───────────────┴──────────────────────────────────────────────────────────────┘
found 2 low severity vulnerabilities in 146959 scanned packages
  2 vulnerabilities require manual review. See the full report for details.

I fails connecting to appium server and start the test, see attached log.
My script looks as follow:
var appiumTizenDriver = require("appium-tizen-driver");

defaultCaps = {
appPackage: '62c6AU3M4C',
deviceName: 'Tizen',
platformName: 'Tizen'
}
var driver = new appiumTizenDriver.TizenDriver()

driver.createSession(defaultCaps);

I see in the log the following:
ERR! SDB Error: Error finding if app is installed. Original error: Error executing sdbExec. Original error: 'Command '/Users/boazwarshawsky/tizen-studio/tools/sdb -s 192.168.70.85:26101 shell 'app_launcher --list | grep 62c6AU3M4C'' exited with code 1'; Stderr: 'closed'; Code: '1'
E

Depending on jimp at 0.5.3 introduces a vulnerability through the dependency chain.

GHSA-vh95-rmgr-6w4m

Currently running version 1.1.1-beta.4. Two packages, [email protected] and [email protected] are causing the following warnings.

yarn audit v1.22.5

│ low           │ Prototype Pollution 
│ Package       │ minimist
│ Patched in    │ >=0.2.1 <1.0.0 || >=1.2.3
│ Dependency of │ appium
│ Path          │ appium > appium-tizen-driver > jimp > @jimp/custom > @jimp/core > mkdirp > minimist
│ More info     │ https://www.npmjs.com/advisories/1179

│ low           │ Prototype Pollution 
│ Package       │ yargs-parser
│ Patched in    │ >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2
│ Dependency of │ appium
│ Path          │ appium > appium-tizen-driver > yargs > yargs-parser
│ More info     │ https://www.npmjs.com/advisories/1500 

Currently working around by adding appropriate resolutions (below) to the package.json file, but I am curious as to when fixes for both might be seen.

"resolutions": {
        "appium/**/minimist": "^0.2.1",
        "appium/**/yargs-parser": "^18.1.2"
}