Code Monkey home page Code Monkey logo

appium-tizen-tv-driver's Introduction

appium-tizen-tv-driver's People

Contributors

boneskull avatar jlipps avatar kazucocoa avatar mattfldev avatar renovate[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

mattfldev

appium-tizen-tv-driver's Issues

server-side error occurred while processing the command: Could not find a driver for automationName 'Appium' and platformName TizenTV'

Issue:
Could not find a driver for automationName 'Appium' and platformName TizenTV'

Setup details:
Have added this appium-tizen-tv-driver to [email protected] version by using following commend
appium driver install --source=npm appium-tizen-tv-driver

Used Appium-Python-Client 2.6.0
executed following code

Code

from appium import webdriver
import time
driver = webdriver.Remote(
    command_executor='http://127.0.0.1:4723',
    desired_capabilities={
        "platformName": "TizenTV",
        'deviceName': 'SamsungTV',
        'deviceAddress': 'IP address ',
        'deviceMac' : 'MAC address,
        'udid': 'UUIDL',
        'appPackage': 'PackageID',
        'chromedriverExecutable' : 'Path'
        'isDeviceApiSsl': 'True',
        'app': 'KaveriOnTizen',
        'automationName': 'Appium'

    })

print(driver.press_button("down")) 
  
Console output:
/Users/agopichand/projects/appium/venv/bin/python /Users/agopichand/projects/appium/connect.py
Traceback (most recent call last):
  File "/Users/agopichand/projects/appium/connect.py", line 3, in <module>
    driver = webdriver.Remote(
  File "/Users/agopichand/projects/appium/venv/lib/python3.9/site-packages/appium/webdriver/webdriver.py", line 229, in __init__
    super().__init__(
  File "/Users/agopichand/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 277, in __init__
    self.start_session(capabilities, browser_profile)
  File "/Users/agopichand/projects/appium/venv/lib/python3.9/site-packages/appium/webdriver/webdriver.py", line 319, in start_session
    response = self.execute(RemoteCommand.NEW_SESSION, w3c_caps)
  File "/Users/agopichand/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 435, in execute
    self.error_handler.check_response(response)
  File "/Users/agopichand/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 247, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Could not find a driver for automationName 'Appium' and platformName TizenTV'. Have you installed a driver that supports those capabilities? Run 'appium driver list --installed' to see. (Lower-level error: Could not find installed driver to support given caps)
Stacktrace:
UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not find a driver for automationName 'Appium' and platformName TizenTV'. Have you installed a driver that supports those capabilities? Run 'appium driver list --installed' to see. (Lower-level error: Could not find installed driver to support given caps)
    at getResponseForW3CError (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/errors.js:956:9)
    at asyncHandler (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:428:35)

[feature] add tizentv: listApps extension commands

The result is below, thus it may need to parse the result properly but it would be helpful to check installed apps.

	Application List for user 5001
	User's Application
	 Name 	 AppID
	=================================================
	'HdmiCec'	 'org.tizen.hdmicec'
	'automation-app'	 'org.tizen.automation-app'
	'dtv-org.tizen.UsbSyncDisplay'	 'org.tizen.UsbSyncDisplay'
	'뉴스리듬'	 'jObNpkM9m9.newsrhythm'
        ...
	'ResourceNormalAITech'	 'com.samsung.tv.coba.setting.aitech.res.normal'
	'samsung-pass'	 'com.samsung.tizen.samsung-pass-agent'
	'UBDetail'	 'com.samsung.tv.UBDetail'
	'NetworkSetting-Tizen'	 'org.tizen.NetworkSetting-Tizen'
	'NetworkSpeaker'	 'org.tizen.NetworkSpeaker'
	'Setting'	 'com.samsung.tv.coba.setting'
	'register-device-ux'	 'org.tizen.register-device-ux'
	'Fitplan'	 'IohB833qj0.Fitplan'
	'ResourceTizen30'	 'com.samsung.tv.csfs.res.tizen30'
	'service-application'	 'org.tizen.litewebappservice'
	'Internal Demo Player'	 'org.tizen.internal-demo-player-tv'
	'Apple AirPlay'	 'NRi6kdBYJ0.AirPlayWebApp'
	'usb-launcher-tv'	 'org.tizen.usb-launcher-tv'
	'Apple TV'	 'com.samsung.tv.aria-video'
	'AVControl'	 'org.tizen.AVControl'
	'Add_Channels'	 'org.tizen.Add_Channels'
	'acr-service-app'	 'org.tizen.acr-service-app'
	'EasySetup-Daemon'	 'org.tizen.easysetup-daemon'
	'SafLaunchBridge'	 'com.samsung.tv.safLaunchBridge'
	'ipcontrol-service-atsc'	 'com.samsung.tv.ipcontrol-dservice-atsc'
	'com.samsung.tv.searchall'	 'com.samsung.tv.searchall'
	'Youtube'	 'com.samsung.tv.cobalt-yt'
	'Notification'	 'com.samsung.tv.coba.notification'
	'Sling TV'	 'ZmmGjO6VKO.slingtv'
	'emanual-app'	 'org.tizen.emanual-app'
	'Remoteworkspace'	 'com.samsung.tv.coba.remoteworkspace'
	'ep-hotel-factory'	 'org.tizen.ep-hotel-factory'
	'sound-test'	 'org.tizen.sound-test'
	'Photo player'	 'org.tizen.photo-player-tv'
	'RSCM ScreenSaver'	 'org.tizen.rscm-screensaver'
	'schedule-manager'	 'org.tizen.schedule-manager'
	'hdmi-troubleshooting'	 'com.samsung.tv.hdmi-troubleshooting'
	'av-sync-service'	 'com.samsung.tv.av-sync-service'
	'com.samsung.tv.preview-downloader'	 'com.samsung.tv.preview-downloader'
	'factory'	 'org.tizen.factory'
	'menu'	 'org.tizen.menu'
	'art-app'	 'org.tizen.art-app'
	'TVTodoDemo'	 'Mu89O8r4Lm.TVTodoDemo'
	'HomeSetting'	 'org.tizen.homesetting'
	'com.samsung.tv.aria-engine'	 'com.samsung.tv.aria-engine'
	''	 'org.tizen.tts-engine-vd-sr'
	'Widget Viewer for SDK'	 'org.tizen.widget_viewer_sdk'
	'eFreeRdpUI'	 'org.tizen.efreerdp.ui'
	'IotPreviewd'	 'com.samsung.tv.preview-updater'
	'Apps'	 'org.volt.apps'
	'ContentIndicator'	 'com.samsung.tv.contentindicator'
	'hotelcloning'	 'org.tizen.ephotel-cloning'
	'Netflix'	 'org.tizen.netflix-app'
	'Tizen keyboard'	 'ise-default-tv'
	'ephotel-remote'	 'org.tizen.ep-hotel-popup-ui'
	'stt-client'	 'org.tizen.stt-client'
	'stand-by-scan'	 'org.tizen.stand-by-scan'
	'SmartThings V-Home Service'	 'com.samsung.tv.iot-service-vhome'
	'NotificationApp'	 'com.samsung.tv.notification-app'
	'Sealayer'	 'com.samsung.tv.sealayer'
	'csfs'	 'com.samsung.tv.csfs'
	'ViX: Cine y TV Gratis en Español'	 'n3LrtEeQNd.Univision'
	'QuickEditorApp'	 'com.samsung.ep.hotel-quicksetting-editor'
	'service'	 'gzcc4LRFBF.service'
	'Sync Demo Gui'	 'org.tizen.UsbSyncDisplay.gui'
	'HBO Max'	 'cj37Ni3qXM.HBONow'
	'preview service'	 '3KA0pm7a7V.preview'
	'service-application'	 'rcr-device'
	'ResourceNormal'	 'com.samsung.tv.coba.setting.res.normal'
	'LibAriaFW'	 'lib-ariafw-tv'
	'LiveTV'	 'com.samsung.tv.coba.livetv'
	'ContentServiceManager'	 'ContentServiceManager'
	'App'	 'com.samsung.tv.cobalt-app-8346'
	'slingtvBgservice'	 'ZmmGjO6VKO.slingtvBgservice'
	'airplay-app'	 'com.samsung.tv.airplay-app'
	'Antenna Selection'	 'org.tizen.antenna-selection'
	'Jillian Michaels Fitness App'	 'EMuigH474Q.JillianMichaelsFitnessApp'
	'tv-viewer'	 'org.tizen.tv-viewer'
	'Apps'	 'com.samsung.tv.store'
	'volume-setting'	 'org.tizen.volume-setting'
	'BritBox by BBC & ITV'	 'tCyZuSsCVw.Britbox'
	'com.samsung.tv.bt-mdemanager'	 'com.samsung.tv.bt-mdemanager'
	'Samsung TV Plus'	 'com.samsung.tv.tvPlusDeeplinker'
	'DisneyPlusPreviewService'	 'MCmYXNxgcu.DisneyPlusService'
	'btaudiolist'	 'org.tizen.btaudiolist'
	'RunningAppsService'	 'org.tizen.RunningAppsService'
	'volume'	 'org.tizen.alert-syspopup'
	'App Launcher'	 'aQjWjLsPaO.MultiScreenWebLauncher'
	'RSCM SyncPlayer'	 'org.tizen.rscm-syncplayer'
	'Voice Client'	 'org.tizen.voice-client'
	'App'	 'com.samsung.tv.cobalt-app-3436'
	'isf-kbd-mode-changer'	 'org.tizen.isf-kbd-mode-changer'
	'Gallery'	 'com.samsung.tv.gallery'
	'Resourcedevicemanager'	 'com.samsung.tv.coba.setting.devicemanager.res'
	'Jellyfin'	 'AprZAARz4r.Jellyfin'
	'bbplayer'	 'com.samsung.tv.bbplayer'
	'airplay-service'	 'com.samsung.tv.airplay-service'
	'HereMaps UC'	 'org.tizen.heremaps-uc'
	'AmbientSetting'	 'com.samsung.tv.ambientsetting'
	'mbr-daemon'	 'org.tizen.mbr-daemon'
	'BuiltInAppUpgrader'	 'com.samsung.tv.built-in-app-upgrader'
	'TV App autosetup-channel-list'	 'com.samsung.tv.autosetup-channel-list'
	'Apps'	 'com.samsung.tv.coba.apps'
	'samsung-analytics'	 'com.samsung.tizen.samsung-analytics'
	'Remote Management'	 'org.tizen.remote-management'
	'sample-sys-popup'	 'org.tizen.pvrrecorder-syspopup'
	'App'	 'com.samsung.tv.cobalt-app-2146'
	''	 'org.tizen.reminder'
	'Smarthub Connection Test'	 'org.tizen.smarthub-connection-test'
	' Network status widget '	 'org.tizen.rs-network-status'
	'TV App MBRApp'	 'org.tizen.mbr-app'
	'QVC and HSN Streaming Service'	 'LImG0QPABV.QXHMarketplace'
	'SamsungAccountService'	 'com.samsung.tizen.samsung-account'
	'wizard'	 'org.tizen.wizard'
	'bnr-service'	 'capi-bnr-tv'
	'AmbientApp'	 'org.tizen.ambientapp'
	'SliveProviderDaemon'	 'com.samsung.tv.slive-daemon'
	'Spotify Service'	 'rJeHak5zRg.SpotifyService'
	'VUDUTilesService'	 'kk8MbItQ0H.TilesService'
	'Freevee'	 'OK2Rdkjmsi.IMDbTV'
	'Key grab'	 'org.tizen.UsbSyncDisplay.keygrab'
	'Search'	 'com.samsung.tv.coba.search'
	'Video player'	 'org.tizen.video-player-tv'
	'com.samsung.tv.commonsearch'	 'com.samsung.tv.commonsearch'
	'automation-alert'	 'org.tizen.automation-alert'
        ...
	=================================================

Tizen App installation, run and uninstallation is not working on appium-tizen-tv-driver duo to the wrong paramer -s

Issue:
Tizen App installation, run and uninstallation is not working on appium-tizen-tv-driver due to the wrong parameter '-s'

Expected parameter for TIZEN CLI commend

tizen install -n name -t UUID -- ~/path
tizen run -p packageName -t UUID
tizen uninstall -p packageName -t UUID

Verified above commends on tizen CLI, those are working

wrong commends with -s parameter
Administrators-MacBook-Pro:bin $ tizen run -p -s
There is no target.
Can not get the target option.

Correct commend wiht -t parameter
Administrators-MacBook-Pro:bin $ tizen run -p -t
Launching the Tizen application...

Platform log view

... successfully launched pid = 1049 with debug 0
Tizen application is successfully launched.

Setup details:
Have added this appium-tizen-tv-driver to [email protected] version by using following commend
appium driver install --source=npm appium-tizen-tv-driver

Used Appium-Python-Client 2.6.0

executed following code

Desired capabilities:

driver = webdriver.Remote(
    command_executor='http://127.0.0.1:4723',
    desired_capabilities={
        "platformName": "TizenTV",
        'deviceName': 'SamsungTV',
        'deviceAddress': 'Device IP',
        'deviceMac' : 'Device Mac Address,
        'udid': 'uuid',
        'appPackage': 'app package name',
        'chromedriverExecutable': '/path,
        'isDeviceApiSsl': True,
        'app': '/path',
        'automationName': 'TizenTV',
        'noReset': True
    })

Console output:

Traceback (most recent call last):
  File "/Users/username/projects/appium/connect.py", line 3, in <module>
    driver = webdriver.Remote(
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/appium/webdriver/webdriver.py", line 229, in __init__
    super().__init__(
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 277, in __init__
    self.start_session(capabilities, browser_profile)
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/appium/webdriver/webdriver.py", line 319, in start_session
    response = self.execute(RemoteCommand.NEW_SESSION, w3c_caps)
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 435, in execute
    self.error_handler.check_response(response)
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 247, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Command '/Users/username/tizen-studio/tools/ide/bin/tizen install -n ~/projects/path  -s UUID' exited with code 1. Stdout was: 'There is no UUID  target. Total time: 00:00:00.469
'. Stderr was: ''
Stacktrace:
UnknownError: An unknown server-side error occurred while processing the command. Original error: Command '/Users/username/tizen-studio/tools/ide/bin/tizen install -n ~/projects/path -s UUID' exited with code 1. Stdout was: 'There is no UUID target. Total time: 00:00:00.469
'. Stderr was: ''
    at getResponseForW3CError (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/errors.js:956:9)
    at asyncHandler (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:428:35)

Tizen CLI 2.5.25 version

Please fix this issue as soon as possible.

inconsistent "mode" capabilities

Does it make sense to have both rcMode and rcSendKeysStrategy? I don't think it does. It would seem that rcMode: <proxy|remote> would be sufficient, and control both regular key presses and text input behavior.

I'd also like to rename rcMode js to proxy

@jlipps

Process is not getting terminating if driver.findElement not able to fine the element.

Have following setup :
[email protected]
Appium (v2.0.0-beta.40)
Appium-Python-Client 2.6.0

Have following code:
from appium import webdriver
from selenium.webdriver.common.by import By
import time

driver = webdriver.Remote(
command_executor='http://127.0.0.1:4723',
desired_capabilities={
'appPackage': 'appPackage',
'automationName': 'TizenTV',
"platformName": "TizenTV",
'deviceAddress': 'IP Address'
'deviceMac': 'Mac Address',
'chromedriverExecutable': 'Path to driver ',
'deviceName': 'device unique number ',
'udid': 'IP and Port',
'app': 'app location ',

})

print("The current app title:", driver.title)

print("Press DOWN", driver.press_keycode("DOWN"))
print("Check main app frame is enabled:",driver.find_element(By.ID, "appFrame4").is_enabled())

print("The current app title:", driver.title)
print("Press DOWN", driver.press_keycode("DOWN"))
print("Check main app frame is enabled:",driver.find_element(By.ID, "appFrame4").is_enabled())

Issue :

Program execution stuck at 'print("Check main app frame is enabled:",driver.find_element(By.ID, "appFrame4").is_enabled())' this step and it is going to freeze state forever.

Since appFrame4 element is not presented and appium server is not giving any error to tizenTV driver so program is going for freeze state.

Appium server logs :
Administrators-MacBook-Pro:1 username$ appium
WARN Appium Appium encountered 2 warnings while validating drivers found in manifest /Users/username/.appium/node_modules/.cache/appium/extensions.yaml
WARN Appium Driver "tizentv" has 1 potential problem:
WARN Appium - Driver "tizentv" (package appium-tizen-tv-driver) may be incompatible with the current version of Appium (v2.0.0-beta.40) due to an invalid or missing peer dependency on Appium. Please ask the developer of appium-tizen-tv-driver to add a peer dependency on ^[email protected].
[Appium] Welcome to Appium v2.0.0-beta.40
[Appium] Attempting to load driver tizentv...
[debug] [Appium] Requiring driver at /Users/username/.appium/node_modules/appium-tizen-tv-driver
[Appium] Attempting to load driver xcuitest...
[debug] [Appium] Requiring driver at /Users/username/.appium/node_modules/appium-xcuitest-driver
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[Appium] Available drivers:
[Appium] - [email protected] (automationName 'TizenTV')
[Appium] - [email protected] (automationName 'XCUITest')
[Appium] Available plugins:
[Appium] - [email protected]
[Appium] No plugins activated. Use the --use-plugins flag with names of plugins to activate
[HTTP] --> POST /session
[HTTP] {"capabilities":............
[debug] [AppiumDriver@029d] Calling AppiumDriver.createSession() with args: [.............
[debug] [AppiumDriver@029d] Event 'newSessionRequested' logged at 1659104549605 (19:52:29 GMT+0530 (India Standard Time))
[Appium] Attempting to find matching driver for automationName 'TizenTV' and platformName 'TizenTV'
[Appium] The 'tizentv' driver was installed and matched caps.
[Appium] Will require it at /Users/username/.appium/node_modules/appium-tizen-tv-driver
[debug] [Appium] Requiring driver at /Users/username/.appium/node_modules/appium-tizen-tv-driver
[AppiumDriver@029d] Appium v2.0.0-beta.40 creating new TizenTVDriver (v0.3.0) session
[AppiumDriver@029d] Checking BaseDriver versions for Appium and TizenTVDriver
[AppiumDriver@029d] Appium's BaseDriver version is 8.5.7
[AppiumDriver@029d] TizenTVDriver's BaseDriver version is 8.0.0-beta.6
[BaseDriver] Appium received (M)JSONWP desired capabilities in alongside the W3C capabilities; they will be ignored
[debug] [BaseDriver] Creating session with W3C capabilities: {
[debug] [BaseDriver] "alwaysMatch": {
[debug] [BaseDriver] "platformName": "TizenappPackageTV",
[debug] [BaseDriver] "appium:appPackage": "",
[debug] [BaseDriver] "appium:automationName": "TizenTV",
[debug] [BaseDriver] "appium:deviceAddress": "IP",
[debug] [BaseDriver] "appium:deviceMac": "MAC",
[debug] [BaseDriver] "appium:chromedriverExecutable": "/Users/username/Desktop/1/chromedriver",
[debug] [BaseDriver] "appium:deviceName": "DeviceName",
[debug] [BaseDriver] "appium:udid": "IP",
[debug] [BaseDriver] "appium:app": "/projects",
[debug] [BaseDriver] "appium:rcPairingMode": "true"
[debug] [BaseDriver] },
[debug] [BaseDriver] "firstMatch": [
[debug] [BaseDriver] {}
[debug] [BaseDriver] ]
[debug] [BaseDriver] }
[BaseDriver] Session created with session id: 4d8c4dba-072c-46bc-a517-94764e32c342
[TizenTVDriver] Uninstalling tizen app 'packageName' on device 'IP'
[TizenTVDriver] Attempting to verify location of the 'tizen' binary
[TizenTVDriver] Binary was found at /Users/username/tizen-studio/tools/ide/bin/tizen
[TizenTVDriver] Running command: /Users/username/tizen-studio/tools/ide/bin/tizen uninstall -p packageName -s IP
[TizenTVDriver] Installing tizen app '/projects/ path on device 'IP'
[TizenTVDriver] Running command: /Users/username/tizen-studio/tools/ide/bin/tizen install -n /projects/ -s IP
[TizenTVDriver] Starting packageName in debug mode on IP
[TizenTVDriver] Attempting to verify location of the 'sdb' binary
[TizenTVDriver] Binary was found at /Users/username/tizen-studio/tools/sdb
[TizenTVDriver] Running command: /Users/username/tizen-studio/tools/sdb -s IP shell 0 debug packageName
[TizenTVDriver] Debug port opened on 53224
[TizenTVDriver] Chose local port 8001 for remote debug communication
[TizenTVDriver] Forwarding local TCP port 8001 to port 53224 on device IP
[TizenTVDriver] Running command: /Users/username/tizen-studio/tools/sdb -s 1 IP forward tcp:8001 tcp:53224
[debug] [Chromedriver] Changed state to 'starting'
[Chromedriver] Set chromedriver binary as: /Users/username/Desktop/1/chromedriver
[debug] [Chromedriver] Killing any old chromedrivers, running: pkill -15 -f "/Users/username/Desktop//1/chromedriver.*--port=8002"
[Chromedriver] No old chromedrivers seem to exist
[Chromedriver] Spawning chromedriver with: /Users/username/Desktop//1/chromedriver --url-base=wd/hub --port=8002 --verbose
[debug] [Chromedriver] Chromedriver version: '2.36.540469'
[debug] [Chromedriver] Chromedriver v. 2.36.540469 does not fully support W3C protocol. Defaulting to MJSONWP
[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8002/wd/hub/status] with no body
[debug] [WD Proxy] Got response with status 200: {"sessionId":"","status":0,"value":{"build":{"version":"alpha"},"os":{"arch":"x86_64","name":"Mac OS X","version":"10.16.0"}}}
[Chromedriver] Starting MJSONWP Chromedriver session with capabilities: {
[Chromedriver] "desiredCapabilities": {
[Chromedriver] "goog:chromeOptions": {
[Chromedriver] "debuggerAddress": "127.0.0.1:8001"
[Chromedriver] },
[Chromedriver] "loggingPrefs": {
[Chromedriver] "browser": "ALL"
[Chromedriver] }
[Chromedriver] }
[Chromedriver] }
[debug] [WD Proxy] Matched '/session' to command name 'createSession'
[debug] [WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8002/wd/hub/session] with body: {"desiredCapabilities":{"goog:chromeOptions":{"debuggerAddress":"127.0.0.1:8001"},"loggingPrefs":{"browser":"ALL"}}}
[debug] [Chromedriver] Webview version: 'Chrome/76.0.3809.146'
[debug] [WD Proxy] Got response with status 200: {"sessionId":"f95ceb63174ea90079e72eec3f4bd187","status":0,"value":{"acceptInsecureCerts":false,"acceptSslCerts":false,"applicationCacheEnabled":false,"browserConnectionEnabled":false,"browserName":"chrome","chrome":{"chromedriverVersion":"2.36.540469 (1881fd7f8641508feb5166b7cae561d87723cfa8)"},"cssSelectorsEnabled":true,"databaseEnabled":false,"handlesAlerts":true,"hasTouchScreen":false,"javascriptEnabled":true,"locationContextEnabled":true,"mobileEmulationEnabled":false,"nativeEvents":true,"pageLoadStrategy":"normal","platform":"","rotatable":false,"setWindowRect":false,"takesHeapSnapshot":true,"takesScreenshot":true,"unexpectedAlertBehaviour":"","version":"76.0.3809.146","webStorageEnabled":true}}
[WD Proxy] Determined the downstream protocol as 'MJSONWP'
[debug] [Chromedriver] Changed state to 'online'
[TizenTVDriver] Waiting for app launch to take effect
[TizenTVDriver] Clearing app local storage
[debug] [WD Proxy] Matched '/execute/sync' to command name 'execute'
[Protocol Converter] Rewrote the original URL '/execute/sync' to '/execute' for MJSONWP protocol
[debug] [WD Proxy] Proxying [POST /execute] to [POST http://127.0.0.1:8002/wd/hub/session/f95ceb63174ea90079e72eec3f4bd187/execute] with body: {"script":"window.localStorage.clear()","args":[]}
[debug] [WD Proxy] Got response with status 200: {"sessionId":"f95ceb63174ea90079e72eec3f4bd187","status":0,"value":null}
[TizenTVDriver] Reloading page
[debug] [WD Proxy] Matched '/execute/sync' to command name 'execute'
[Protocol Converter] Rewrote the original URL '/execute/sync' to '/execute' for MJSONWP protocol
[debug] [WD Proxy] Proxying [POST /execute] to [POST http://127.0.0.1:8002/wd/hub/session/f95ceb63174ea90079e72eec3f4bd187/execute] with body: {"script":"window.location.reload()","args":[]}
[debug] [WD Proxy] Got response with status 200: {"sessionId":"f95ceb63174ea90079e72eec3f4bd187","status":0,"value":null}
[AppiumDriver@029d] New TizenTVDriver session created successfully, session 4d8c4dba-072c-46bc-a517-94764e32c342 added to master session list
[debug] [AppiumDriver@029d] Event 'newSessionStarted' logged at 1659104573482 (19:52:53 GMT+0530 (India Standard Time))
[debug] [TizenTVDriver@4d7f219f (4d8c4dba)] Cached the protocol value 'W3C' for the new session 4d8c4dba-072c-46bc-a517-94764e32c342
[debug] [TizenTVDriver@4d7f219f (4d8c4dba)] Responding to client with driver.createSession() result: {"....."
[HTTP] <-- POST /session 200 23883 ms - 480
[HTTP]
[HTTP] --> GET /session/4d8c4dba-072c-46bc-a517-94764e32c342/title
[HTTP] {}
[TizenTVDriver@4d7f219f (4d8c4dba)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/session/4d8c4dba-072c-46bc-a517-94764e32c342/title' to command name 'title'
[debug] [WD Proxy] Proxying [GET /session/4d8c4dba-072c-46bc-a517-94764e32c342/title] to [GET http://127.0.0.1:8002/wd/hub/session/f95ceb63174ea90079e72eec3f4bd187/title] with no body
[debug] [WD Proxy] Got response with status 200: {"sessionId":"f95ceb63174ea90079e72eec3f4bd187","status":0,"value":"project on Tizen"}
[WD Proxy] Replacing sessionId f95ceb63174ea90079e72eec3f4bd187 with 4d8c4dba-072c-46bc-a517-94764e32c34
[HTTP] <-- GET /session/4d8c4dba-072c-46bc-a517-94764e32c342/title 200 41 ms - 89
[HTTP]
[HTTP] --> POST /session/4d8c4dba-072c-46bc-a517-94764e32c342/element
[HTTP] {"using":"id","value":"appFrame4"}
[TizenTVDriver@4d7f219f (4d8c4dba)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/session/4d8c4dba-072c-46bc-a517-94764e32c342/element' to command name 'findElement'
[debug] [WD Proxy] Proxying [POST /session/4d8c4dba-072c-46bc-a517-94764e32c342/element] to [POST http://127.0.0.1:8002/wd/hub/session/f95ceb63174ea90079e72eec3f4bd187/element] with body: {"using":"id","value":"appFrame4"}
[debug] [WD Proxy] Got response with status 200: {"sessionId":"f95ceb63174ea90079e72eec3f4bd187","status":7,"value":{"message":"no such element: Unable to locate element: {"method":"id","selector":"appFrame4"}\n (Session info: chrome=76.0.3809.146)\n (Driver info: chromedriver=2.36.540469 (1881fd7f8641508feb5166b7cae561d87723cfa8),platform=Mac OS X 10.16.0 x86_64)"}}

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • chore(workflows): update actions/checkout digest to 0ad4b8f
  • chore(deps): update dependency webdriverio to v8.36.1
  • fix(appium-tizen-tv-driver): update dependency appium-chromedriver to v5.6.50
  • chore(deps): update dependency mocha to v10.4.0
  • fix(tizen-remote): update dependency ws to v8.17.0
  • chore(deps): update dependency conventional-changelog-conventionalcommits to v8
  • chore(deps): update dependency sinon to v18
  • 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

github-actions
.github/workflows/build.yml
  • actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
  • actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8
  • actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
  • rinchsan/renovate-config-validator v0.2.0@a12a2b98cd4db923c33d1ce407c57afb43f3ff59
npm
package.json
  • @appium/eslint-config-appium 8.0.5
  • @appium/eslint-config-appium-ts 0.3.2
  • @appium/tsconfig 0.3.1
  • @humanwhocodes/env 2.2.2
  • @types/bluebird 3.5.38
  • @types/debug 4.1.8
  • @types/jquery 3.5.17
  • @types/lodash 4.14.197
  • @types/mocha 10.0.1
  • @types/node 18.17.12
  • @types/sinon 10.0.16
  • @types/teen_process 2.0.4
  • @types/yargs 17.0.24
  • @typescript-eslint/eslint-plugin 5.62.0
  • @typescript-eslint/parser 5.62.0
  • appium 2.1.3
  • conventional-changelog-conventionalcommits 7.0.2
  • cross-env 7.0.3
  • eslint 8.57.0
  • eslint-plugin-import 2.29.1
  • eslint-plugin-mocha 10.4.1
  • eslint-plugin-promise 6.1.1
  • get-port 5.1.1
  • lerna 7.4.2
  • midnight-smoker 8.0.0
  • mocha 10.3.0
  • npm-run-all 4.1.5
  • prettier 3.2.5
  • rewiremock 3.14.5
  • sinon 17.0.1
  • ts-node 10.9.2
  • tsd 0.28.1
  • typescript 5.4.5
  • unexpected 13.2.1
  • unexpected-eventemitter 2.4.0
  • unexpected-sinon 11.1.0
  • webdriverio 8.36.0
  • node >=14
  • npm >=8
  • @phenomnomnominal/tsquery 5.0.1
packages/appium-tizen-tv-driver/package.json
  • @appium/types 0.13.4
  • appium-chromedriver 5.6.38
  • asyncbox 3.0.0
  • bluebird 3.7.2
  • get-port 5.1.1
  • got 11.8.6
  • keycode 2.2.1
  • lodash 4.17.21
  • source-map-support 0.5.21
  • teen_process 2.1.1
  • type-fest 3.13.1
  • yargs 17.7.2
  • appium ^2.0.0-beta.46
  • node >=14
  • npm >=6
packages/tizen-remote/package.json
  • @appium/strongbox 0.3.1
  • @humanwhocodes/env 2.2.2
  • @types/node 18.17.12
  • @types/ws 8.5.5
  • debug 4.3.4
  • delay 4.4.1
  • lodash 4.17.21
  • p-retry 4.6.2
  • strict-event-emitter-types 2.0.0
  • type-fest 3.13.1
  • ws 8.16.0
packages/tizen-sample-app/package.json

  • Check this box to trigger a request for Renovate to run again on this repository

Not able to take screenshot on Tizen TV

Please refer to appium/appium#19905

code

BaseOptions options = new BaseOptions()
        .amend("appium:deviceName", "Tizen5.5 2020")
        .amend("platformName", "TizenTV")
        .amend("appium:automationName", "TizenTV")
        .amend("appium:udid", "192.168.10.184:26101")
        .amend("appium:deviceAddress", "192.168.10.184:26101")
        .amend("appium:noReset", false)
        .amend("appium:fullContextList", true)
        .amend("appium:app", "/Users/$USER/aviu/apps/Viu_dev.wgt")
        .amend("appium:chromedriverExecutableDir", "/Users/$USER/aviu/apps/tv/chromedriver/")
        .amend("appium:rcMode", "remote")
        .amend("appium:rcToken", "15615414")
        .amend("appium:appPackage", "TXSXgdzhCp");

driver = new AppiumDriver(new URL("http://127.0.0.1:4723"), options);
// sleep for a while
...
byte[] bytes = ((TakesScreenshot) driver).getScreenshotAs(OutputType.BYTES);

error

Mar 18, 2024 6:38:31 PM org.openqa.selenium.remote.ErrorCodes toStatus
INFO: HTTP Status: '408' -> incorrect JSON status mapping for 'timeout' (500 expected)
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from renderer: 9.999
(Session info: chrome=69.0.3497.128)
(Driver info: chromedriver=2.44.609545 (c2f88692e98ce7233d2df7c724465ecacfe74df5),platform=Mac OS X 10.16.0 x86_64)
Build info: version: '4.18.1', revision: 'b1d3319b48'
System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '14.0', java.version: '17.0.7'
Driver info: io.appium.java_client.AppiumDriver
Command: [16a06b95-908c-4ae5-a9fe-c1eb2aa673fb, screenshot {}]
Capabilities {appium:app: /Users/$USER/aviu/apps/Viu_..., appium:appLaunchCooldown: 3000, appium:appPackage: TXSXgdzhCp, appium:automationName: TizenTV, appium:chromedriverExecutableDir: /Users/$USER/aviu/apps/tv/c..., appium:deviceAddress: 192.168.10.184:26101, appium:deviceName: Tizen5.5 2020, appium:fullContextList: true, appium:noReset: false, appium:rcMode: remote, appium:rcToken: 15615414, appium:udid: 192.168.10.184:26101, platformName: TizenTV}
Session ID: 16a06b95-908c-4ae5-a9fe-c1eb2aa673fb
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at org.openqa.selenium.remote.ErrorCodec.decode(ErrorCodec.java:167)
at org.openqa.selenium.remote.codec.w3c.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:138)
at org.openqa.selenium.remote.codec.w3c.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:50)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:190)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:237)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:519)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:592)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:307)
at org.openqa.selenium.remote.RemoteWebDriver.getScreenshotAs(RemoteWebDriver.java:322)
at io.appium.java_client.AppiumDriver.getScreenshotAs(AppiumDriver.java:316)
at steps.tizenTVDemoStepDef.afterScenario(tizenTVDemoStepDef.java:59)

logs

https://gist.github.com/Jiyvn/755599c542a3475eaf399473161b3a1c

Not able to start session

Hello, I have setup this driver using WebdriverIO, but I am not able to start session always getting error below

[0-0] 2023-09-20T13:08:27.637Z ERROR @wdio/runner: Error: Failed to create session.
[0-0] An unknown server-side error occurred while processing the command. Original error: Command '/Users/pauliusguzas/tizen-studio/tools/sdb -s 192.168.1.29\:26101 shell 0 debug my.cool.app.id' exited with code 1. Stdout was: ''. Stderr was: 'closed '

These are my capabilities:

      {
            platformName: 'TizenTV',
            'appium:options': {
                automationName: 'TizenTV',
                deviceName: '192.168.1.29:26101',
                chromedriverExecutable: '/Users/pauliusguzas/Downloads/chromedriver',
                appPackage: 'my.cool.app.id',
                app: 'path/to/my/app.wgt',
                fullReset: true,
            },
        },

Versions used:

        "@wdio/allure-reporter": "7.19.5",
        "@wdio/appium-service": "7.19.5",
        "@wdio/cli": "7.19.5",
        "@wdio/local-runner": "7.19.5",
        "@wdio/mocha-framework": "7.19.5",
        "@wdio/selenium-standalone-service": "7.19.5",
        "@wdio/spec-reporter": "7.19.5",
        "allure-commandline": "2.17.2",
        "appium": "2.0.0",
        "appium-mac2-driver": "1.7.2",
        "appium-uiautomator2-driver": "2.29.5",
        "appium-xcuitest-driver": "4.32.11",
        "appium-tizen-tv-driver": "0.8.1",
        "appium-lg-webos-driver": "0.0.6",
        "chromedriver": "102.0.0",
        "wdio-chromedriver-service": "7.2.2",
        "wdio-image-comparison-service": "5.0.3",
        "wdio-native-app-compare-service": "2.1.0"

Request: Example of how to use Appium Tizen TV driver on a Samsung TV

Hi team,

How are you all? Hope everyone is doing well.

Firstly, thank you for creating this fantastic repo. I was looking at the driver documentation and got lost!

Please provide an example of how one can implement it in a real scenario. I am familiar with appium for mobile devices, but I want to implement this on a Samsung TV.

A couple of questions about the driver:

  1. After installation, can we inspect the TV's elements? For instance, can we view the app ID and buttons if it is a browser app on the TV?
  2. Or is it only meant to be used as a replacement for the TV remote?

Logs endpoint operation

Background: https://stackoverflow.com/questions/54403756/missing-logs-for-tizen-application-sdb-shows-nothing

Maybe sdb dlog stuff does not work on TV devices to collect device logs, instead, I wonder if we can collect something logs via chromedriver's log endpoints:

https://github.com/appium/appium/blob/master/packages/base-driver/lib/protocol/routes.js#L716-L730

  // Selenium 4 clients
  '/session/:sessionId/se/log': {
    POST: {command: 'getLog', payloadParams: {required: ['type']}},
  },
  // Selenium 4 clients
  '/session/:sessionId/se/log/types': {
    GET: {command: 'getLogTypes'},
  },
  // mjsonwire, appium clients
  '/session/:sessionId/log': {
    POST: {command: 'getLog', payloadParams: {required: ['type']}},
  },
  // mjsonwire, appium clients
  '/session/:sessionId/log/types': {
    GET: {command: 'getLogTypes'},
  },

Not sure if these log endpoint can return meaning full log data, but maybe its better than nothing

Unable to run main TV app in Chrome browser

Hi team,

Can you please help me to check, why we are unable to run our TV app in the Chrome browser.

Appium verson: 2.0.0-beta.46
Windows 10: 21H2

Steps taken:

  1. This is the script we used:
const wd = require("webdriverio");

async function main() {
  const driver = await wd.remote({
    port: 4723,
    capabilities: {
      platformName: "TizenTV",
      "appium:automationName": "TizenTV",
      "appium:deviceName": "10.0.0.41:26101",
      "appium:chromedriverExecutable":
        "C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe",
      "appium:noReset": true,
      "appium:appPackage": "agsyterusi8.HTML5",
    },
  });

  let page = await driver.getPageSource();
  console.log(page);
}

main(); 
  1. After running the code above. We get this page:

image

Below are the appium logs:

[Appium] Welcome to Appium v2.0.0-beta.46
[Appium] Attempting to load driver tizentv...
[debug] [Appium] Requiring driver at C:\Users\ckk\.appium\node_modules\appium-tizen-tv-driver
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[Appium] Available drivers:
[Appium]   - [email protected] (automationName 'TizenTV')
[Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
[HTTP] --> POST /session
[HTTP] {"capabilities":{"alwaysMatch":{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"10.0.0.41:26101","appium:chromedriverExecutable":"C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe","appium:noReset":true,"appium:appPackage":"agsyterusi8.HTML5"},"firstMatch":[{}]},"desiredCapabilities":{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"10.0.0.41:26101","appium:chromedriverExecutable":"C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe","appium:noReset":true,"appium:appPackage":"agsyterusi8.HTML5"}}
[debug] [AppiumDriver@81c7] Calling AppiumDriver.createSession() with args: [{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"10.0.0.41:26101","appium:chromedriverExecutable":"C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe","appium:noReset":true,"appium:appPackage":"agsyterusi8.HTML5"},null,{"alwaysMatch":{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"10.0.0.41:26101","appium:chromedriverExecutable":"C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe","appium:noReset":true,"appium:appPackage":"agsyterusi8.HTML5"},"firstMatch":[{}]}]
[debug] [AppiumDriver@81c7] Event 'newSessionRequested' logged at 1668708643305 (18:10:43 GMT+0000 (Western European Standard Time))
[Appium] Attempting to find matching driver for automationName 'TizenTV' and platformName 'TizenTV'
[Appium] The 'tizentv' driver was installed and matched caps.
[Appium] Will require it at C:\Users\ckk\.appium\node_modules\appium-tizen-tv-driver
[debug] [Appium] Requiring driver at C:\Users\ckk\.appium\node_modules\appium-tizen-tv-driver
[AppiumDriver@81c7] Appium v2.0.0-beta.46 creating new TizenTVDriver (v0.7.3) session
[AppiumDriver@81c7] Checking BaseDriver versions for Appium and TizenTVDriver
[AppiumDriver@81c7] Appium's BaseDriver version is 8.7.3
[AppiumDriver@81c7] TizenTVDriver's BaseDriver version is 8.7.3
[debug] [TizenTVDriver@b819] Creating session with W3C capabilities: {
[debug] [TizenTVDriver@b819]   "alwaysMatch": {
[debug] [TizenTVDriver@b819]     "platformName": "TizenTV",
[debug] [TizenTVDriver@b819]     "appium:automationName": "TizenTV",
[debug] [TizenTVDriver@b819]     "appium:deviceName": "10.0.0.41:26101",
[debug] [TizenTVDriver@b819]     "appium:chromedriverExecutable": "C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe",
[debug] [TizenTVDriver@b819]     "appium:noReset": true,
[debug] [TizenTVDriver@b819]     "appium:appPackage": "agsyterusi8.HTML5"
[debug] [TizenTVDriver@b819]   },
[debug] [TizenTVDriver@b819]   "firstMatch": [
[debug] [TizenTVDriver@b819]     {}
[debug] [TizenTVDriver@b819]   ]
[debug] [TizenTVDriver@b819] }
[TizenTVDriver@b819 (7673576c)] Session created with session id: 7673576c-8c82-4f81-b735-257215bea654
[TizenTVDriver] No udid and/or deviceAddress provided; attempting to derive from deviceName "10.0.0.41:26101"
[debug] [TizenTVDriver] Setting deviceAddress to "10.0.0.41"
[debug] [TizenTVDriver] Setting udid to "10.0.0.41:26101"
[TizenTVDriver] Running tizen app 'org.tizen.browser' on device '10.0.0.41:26101'
[TizenTVDriver] Attempting to verify location of the 'tizen' binary
[TizenTVDriver] Binary was found at C:\tizen-studio\tools\ide\bin\tizen.bat
[TizenTVDriver] Running command: C:\tizen-studio\tools\ide\bin\tizen.bat run -p org.tizen.browser -s 10.0.0.41:26101
[TizenTVDriver] Starting agsyterusi8.HTML5 in debug mode on 10.0.0.41:26101
[TizenTVDriver] Attempting to verify location of the 'sdb' binary
[TizenTVDriver] Binary was found at C:\tizen-studio\tools\sdb.exe
[TizenTVDriver] Running command: C:\tizen-studio\tools\sdb.exe -s 10.0.0.41:26101 shell 0 debug agsyterusi8.HTML5
[TizenTVDriver] Debug port opened on 45585
[TizenTVDriver] Chose local port 10076 for remote debug communication
[TizenTVDriver] Forwarding local TCP port 10076 to port 45585 on device 10.0.0.41:26101
[TizenTVDriver] Running command: C:\tizen-studio\tools\sdb.exe -s 10.0.0.41:26101 forward tcp:10076 tcp:45585
[debug] [Chromedriver@c0fb] Changed state to 'starting'
[Chromedriver@c0fb] Set chromedriver binary as: C:\Users\ckk\Downloads\appiumWithJS\chromedriver.exe
[debug] [Chromedriver@c0fb] Killing any old chromedrivers, running: wmic process where "commandline like '%chromedriver.exe%--port=10081%'" delete
[debug] [Chromedriver@c0fb] Successfully cleaned up old chromedrivers
[Chromedriver@c0fb] Spawning chromedriver with: C:\Users\ckk\Downloads\appiumWithJS\chromedriver.exe --port=10081 --verbose
[debug] [Chromedriver@c0fb] Chromedriver version: '2.29.461591'
[debug] [Chromedriver@c0fb] Chromedriver v. 2.29.461591 does not fully support W3C protocol. Defaulting to MJSONWP
[debug] [Chromedriver@c0fb] Matched '/status' to command name 'getStatus'
[debug] [Chromedriver@c0fb] Proxying [GET /status] to [GET http://127.0.0.1:10081/status] with no body
[debug] [Chromedriver@c0fb] Got response with status 200: {"sessionId":"","status":0,"value":{"build":{"version":"alpha"},"os":{"arch":"x86_64","name":"Windows NT","version":"10.0.19044"}}}
[Chromedriver@c0fb] Starting MJSONWP Chromedriver session with capabilities: {
[Chromedriver@c0fb]   "desiredCapabilities": {
[Chromedriver@c0fb]     "goog:chromeOptions": {
[Chromedriver@c0fb]       "debuggerAddress": "127.0.0.1:10076"
[Chromedriver@c0fb]     },
[Chromedriver@c0fb]     "loggingPrefs": {
[Chromedriver@c0fb]       "browser": "ALL"
[Chromedriver@c0fb]     }
[Chromedriver@c0fb]   }
[Chromedriver@c0fb] }
[debug] [Chromedriver@c0fb] Matched '/session' to command name 'createSession'
[debug] [Chromedriver@c0fb] Proxying [POST /session] to [POST http://127.0.0.1:10081/session] with body: {"desiredCapabilities":{"goog:chromeOptions":{"debuggerAddress":"127.0.0.1:10076"},"loggingPrefs":{"browser":"ALL"}}}
[debug] [Chromedriver@c0fb] Webview version: 'Chrome/56.0.2924.87'
[debug] [Chromedriver@c0fb] Got response with status 200: {"sessionId":"b9907c8b4008cc73f36f9f76f86b8061","status":0,"value":{"acceptSslCerts":true,"applicationCacheEnabled":false,"browserConnectionEnabled":false,"browserName":"chrome","chrome":{"chromedriverVersion":"2.29.461591 (62ebf098771772160f391d75e589dc567915b233)","userDataDir":"C:\\Users\\ckk\\AppData\\Local\\Temp\\scoped_dir19124_1022"},"cssSelectorsEnabled":true,"databaseEnabled":false,"handlesAlerts":true,"hasTouchScreen":false,"javascriptEnabled":true,"locationContextEnabled":true,"mobileEmulationEnabled":false,"nativeEvents":true,"networkConnectionEnabled":false,"pageLoadStrategy":"normal","platform":"Windows NT","rotatable":false,"takesHeapSnapshot":true,"takesScreenshot":true,"unexpectedAlertBehaviour":"","version":"56.0.2924.87","webStorageEnabled":true}}
[Chromedriver@c0fb] Determined the downstream protocol as 'MJSONWP'
[debug] [Chromedriver@c0fb (b9907c8b)] Changed state to 'online'
[AppiumDriver@81c7] New TizenTVDriver session created successfully, session 7673576c-8c82-4f81-b735-257215bea654 added to master session list
[debug] [AppiumDriver@81c7] Event 'newSessionStarted' logged at 1668708651305 (18:10:51 GMT+0000 (Western European Standard Time))
[debug] [TizenTVDriver@b819 (7673576c)] Cached the protocol value 'W3C' for the new session 7673576c-8c82-4f81-b735-257215bea654
[debug] [TizenTVDriver@b819 (7673576c)] Responding to client with driver.createSession() result: {"capabilities":{"appLaunchCooldown":3000,"rcMode":"js","platformName":"TizenTV","automationName":"TizenTV","deviceName":"10.0.0.41:26101","chromedriverExecutable":"C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe","noReset":true,"appPackage":"agsyterusi8.HTML5","deviceAddress":"10.0.0.41","udid":"10.0.0.41:26101"}}
[HTTP] <-- POST /session 200 8010 ms - 386
[HTTP]
[HTTP] --> GET /session/7673576c-8c82-4f81-b735-257215bea654/source
[HTTP] {}
[TizenTVDriver@b819 (7673576c)] Driver proxy active, passing request on via HTTP proxy
[debug] [Chromedriver@c0fb (b9907c8b)] Matched '/session/7673576c-8c82-4f81-b735-257215bea654/source' to command name 'getPageSource'
[debug] [Chromedriver@c0fb (b9907c8b)] Proxying [GET /session/7673576c-8c82-4f81-b735-257215bea654/source] to [GET http://127.0.0.1:10081/session/b9907c8b4008cc73f36f9f76f86b8061/source] with no body
[debug] [Chromedriver@c0fb (b9907c8b)] Got response with status 200: {"sessionId":"b9907c8b4008cc73f36f9f76f86b8061","status":0,"value":"<html xmlns=\"http://www.w3.org/1999/xhtml\"><head></head><body><pre style=\"word-wrap: break-word; white-space: pre-wrap;\"></pre><iframe name=\"chromedriver dummy frame\" src=\"about:blank\"></iframe></body></html>"}
[Chromedriver@c0fb (b9907c8b)] Replacing sessionId b9907c8b4008cc73f36f9f76f86b8061 with 7673576c-8c82-4f81-b735-257215bea654
[HTTP] <-- GET /session/7673576c-8c82-4f81-b735-257215bea654/source 200 51 ms - 279

Expected behavior:
As you can see it looks like it is only opening the browser, is there a way to load the TV app in chrome. We can only do it manually. Below is the image after opening the debug address manually.

image

[OS] Windows: Unable to locate tizen binary file

Hi team,

Can you please help me to resolve the issue listed below:

Used development platform details:

OS Version
Windows 10 21H2 (Build 19044.2130)

Steps to Reproduce

  1. In windows, set TIZEN_HOME as an environment variable —I used (C:\tizen-studio)
  2. Setup main.js with the desired capabilities and run main.js using node

Actual result:

  1. Gives an error, listed below:
C:\Users\ckk\Downloads\appiumWithJS\node_modules\appium-tizen-tv-driver\lib\cli\helpers.js:69
    throw new Error(
          ^
Error: Tried to find binary at C:\tizen-studio\tools\ide\bin\tizen but it did not exist or was not executable. Please double-check permissions and TIZEN_HOME value

Expected result:

  1. Runs the command without errors

Notes:

  1. We tried this on macOS and it works there
  2. On Windows we have a tizen.bat file but on macOS we only have tizen file

Main.js code:

// Import Tizen driver
const tizendio = require("appium-tizen-tv-driver");

async function main() {
  // Create an instance of the TizenTV driver
  const client = new tizendio.TizenTVDriver();

  // Create session

  await client.createSession({
    // Add desired capabilites
    firstMatch: [
      {
        platformName: "TizenTV",
        "appium:automationName": "TizenTV",
        "appium:deviceName": "10.0.0.43:26101",

        // Set chrome driver
        "appium:chromedriverExecutable":
          "C:\\Users\\ckk\\Downloads\\appiumWithJS\\chromedriver.exe",

        // Path to the web app we are trying to install
        "appium:app": "C:\\Users\\ckk\\Downloads\\HTML5.wgt",
        "appium:appPackage": "1",
        "appium:noReset": true,
      },
    ],
  });
}

main();

No preview appearing in Appium Inspector

Does this driver work with Appium Inspector? I am seeing an infinite loading spinner and no preview appearing. The app has loaded successfully on the TV.

Samsung TV 2021

Appium Inspector

  • App version: 2022.7.1
  • Electron: 13.6.9
  • Node.js: 14.16.0

Appium

Capabilities

{
  "platformName": "TizenTV",
  "appium:automationName": "TizenTV",
  "appium:deviceName": "x.x.x.x:26101",
  "appium:chromedriverExecutable": "/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver",
  "appium:appPackage": "wCC7ZHRYCs.demoApp",
  "appium:rcMode": "js",
  "appium:rcToken": "92501415",
  "appium:resetRcToken": "true",
  "appium:rcDebugLog": "true",
  "appium:rcKeypressCooldown": "750"
}

I have started appium using command: appium -p 4723 -pa /wd/hub

I have tried chromedriver 2.38, 2.44, 2.45 and since my TV has Chrome 76, I tried chromedriver76. All the same result

I have also tried changing rcMode from 'js' to 'remote' but the app does not load, so definitely made more progress with this set to 'js'

Screenshot 2023-01-09 at 16 20 36

[Appium] Welcome to Appium v2.0.0-beta.48 (REV 9600617c52d0d2e48493424c529ac6c945d2775b)
[Appium] Non-default server args:
[Appium] {
[Appium]   basePath: '/wd/hub'
[Appium] }
[Appium] Attempting to load driver roku...
[debug] [Appium] Requiring driver at /Users/x/.appium/node_modules/@headspinio/appium-roku-driver
[Appium] Attempting to load driver tizentv...
[debug] [Appium] Requiring driver at /Users/x/.appium/node_modules/appium-tizen-tv-driver
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[Appium] Available drivers:
[Appium]   - [email protected] (automationName 'Roku')
[Appium]   - [email protected] (automationName 'TizenTV')
[Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
[HTTP] --> POST /wd/hub/session
[HTTP] {"capabilities":{"alwaysMatch":{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"172.16.101.198:26101","appium:chromedriverExecutable":"/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver","appium:appPackage":"wCC7ZHRYCs.demoApp","appium:rcMode":"js","appium:rcToken":"92501415","appium:resetRcToken":"true","appium:rcDebugLog":"true","appium:rcKeypressCooldown":"750","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true},"firstMatch":[{}]},"desiredCapabilities":{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"172.16.101.198:26101","appium:chromedriverExecutable":"/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver","appium:appPackage":"wCC7ZHRYCs.demoApp","appium:rcMode":"js","appium:rcToken":"92501415","appium:resetRcToken":"true","appium:rcDebugLog":"true","appium:rcKeypressCooldown":"750","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true}}
[debug] [AppiumDriver@75c4] Calling AppiumDriver.createSession() with args: [{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"172.16.101.198:26101","appium:chromedriverExecutable":"/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver","appium:appPackage":"wCC7ZHRYCs.demoApp","appium:rcMode":"js","appium:rcToken":"92501415","appium:resetRcToken":"true","appium:rcDebugLog":"true","appium:rcKeypressCooldown":"750","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true},null,{"alwaysMatch":{"platformName":"TizenTV","appium:automationName":"TizenTV","appium:deviceName":"172.16.101.198:26101","appium:chromedriverExecutable":"/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver","appium:appPackage":"wCC7ZHRYCs.demoApp","appium:rcMode":"js","appium:rcToken":"92501415","appium:resetRcToken":"true","appium:rcDebugLog":"true","appium:rcKeypressCooldown":"750","appium:newCommandTimeout":3600,"appium:connectHardwareKeyboard":true},"firstMatch":[{}]}]
[debug] [AppiumDriver@75c4] Event 'newSessionRequested' logged at 1673281202167 (16:20:02 GMT+0000 (Greenwich Mean Time))
[Appium] Attempting to find matching driver for automationName 'TizenTV' and platformName 'TizenTV'
[Appium] The 'tizentv' driver was installed and matched caps.
[Appium] Will require it at /Users/x/.appium/node_modules/appium-tizen-tv-driver
[debug] [Appium] Requiring driver at /Users/x/.appium/node_modules/appium-tizen-tv-driver
[AppiumDriver@75c4] Appium v2.0.0-beta.48 creating new TizenTVDriver (v0.7.4) session
[AppiumDriver@75c4] Checking BaseDriver versions for Appium and TizenTVDriver
[AppiumDriver@75c4] Appium's BaseDriver version is 9.1.0
[AppiumDriver@75c4] TizenTVDriver's BaseDriver version is 9.1.0
[debug] [TizenTVDriver@e834] Creating session with W3C capabilities: {
[debug] [TizenTVDriver@e834]   "alwaysMatch": {
[debug] [TizenTVDriver@e834]     "platformName": "TizenTV",
[debug] [TizenTVDriver@e834]     "appium:automationName": "TizenTV",
[debug] [TizenTVDriver@e834]     "appium:deviceName": "172.16.101.198:26101",
[debug] [TizenTVDriver@e834]     "appium:chromedriverExecutable": "/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver",
[debug] [TizenTVDriver@e834]     "appium:appPackage": "wCC7ZHRYCs.demoApp",
[debug] [TizenTVDriver@e834]     "appium:rcMode": "js",
[debug] [TizenTVDriver@e834]     "appium:rcToken": "92501415",
[debug] [TizenTVDriver@e834]     "appium:resetRcToken": "true",
[debug] [TizenTVDriver@e834]     "appium:rcDebugLog": "true",
[debug] [TizenTVDriver@e834]     "appium:rcKeypressCooldown": "750",
[debug] [TizenTVDriver@e834]     "appium:newCommandTimeout": 3600,
[debug] [TizenTVDriver@e834]     "appium:connectHardwareKeyboard": true
[debug] [TizenTVDriver@e834]   },
[debug] [TizenTVDriver@e834]   "firstMatch": [
[debug] [TizenTVDriver@e834]     {}
[debug] [TizenTVDriver@e834]   ]
[debug] [TizenTVDriver@e834] }
[BaseDriver] Number capability passed in as string. Functionality may be compromised.
[TizenTVDriver@e834] Capability 'resetRcToken' changed from string to boolean. This may cause unexpected behavior
[TizenTVDriver@e834] Capability 'rcDebugLog' changed from string to boolean. This may cause unexpected behavior
[TizenTVDriver@e834] Capability 'rcKeypressCooldown' changed from string ('750') to integer (750). This may cause unexpected behavior
[TizenTVDriver@e834] The following capabilities were provided, but are not recognized by Appium:
[TizenTVDriver@e834]   connectHardwareKeyboard
[TizenTVDriver@e834 (d77bbeed)] Session created with session id: d77bbeed-80bb-42fd-8a44-c81862518e20
[TizenTVDriver] No udid and/or deviceAddress provided; attempting to derive from deviceName "172.16.101.198:26101"
[debug] [TizenTVDriver] Setting deviceAddress to "172.16.101.198"
[debug] [TizenTVDriver] Setting udid to "172.16.101.198:26101"
[TizenTVDriver] Running tizen app 'org.tizen.browser' on device '172.16.101.198:26101'
[TizenTVDriver] Attempting to verify location of the 'tizen' binary
[TizenTVDriver] Binary was found at /Users/x/tizen-studio/tools/ide/bin/tizen
[TizenTVDriver] Running command: /Users/x/tizen-studio/tools/ide/bin/tizen run -p org.tizen.browser -s 172.16.101.198:26101
[TizenTVDriver] Starting wCC7ZHRYCs.demoApp in debug mode on 172.16.101.198:26101
[TizenTVDriver] Attempting to verify location of the 'sdb' binary
[TizenTVDriver] Binary was found at /Users/x/tizen-studio/tools/sdb
[TizenTVDriver] Running command: /Users/x/tizen-studio/tools/sdb -s 172.16.101.198:26101 shell 0 debug wCC7ZHRYCs.demoApp
[TizenTVDriver] Debug port opened on 50420
[TizenTVDriver] Chose local port 59877 for remote debug communication
[TizenTVDriver] Forwarding local TCP port 59877 to port 50420 on device 172.16.101.198:26101
[TizenTVDriver] Running command: /Users/x/tizen-studio/tools/sdb -s 172.16.101.198:26101 forward tcp:59877 tcp:50420
[debug] [Chromedriver@dec8] Changed state to 'starting'
[Chromedriver@dec8] Set chromedriver binary as: /Users/x/Projects/AppiumTizen/chromedriver76/chromedriver
[debug] [Chromedriver@dec8] Killing any old chromedrivers, running: pkill -15 -f "/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver.*--port=59882"
[Chromedriver@dec8] No old chromedrivers seem to exist
[Chromedriver@dec8] Spawning chromedriver with: /Users/x/Projects/AppiumTizen/chromedriver76/chromedriver --port=59882 --verbose
[debug] [Chromedriver@dec8] Chromedriver version: '76.0.3809.126'
[debug] [Chromedriver@dec8] Matched '/status' to command name 'getStatus'
[debug] [Chromedriver@dec8] Proxying [GET /status] to [GET http://127.0.0.1:59882/status] with no body
[Chromedriver@dec8] connect ECONNREFUSED 127.0.0.1:59882
[debug] [Chromedriver@dec8] Matched '/status' to command name 'getStatus'
[debug] [Chromedriver@dec8] Proxying [GET /status] to [GET http://127.0.0.1:59882/status] with no body
[debug] [Chromedriver@dec8] Got response with status 200: {"value":{"build":{"version":"76.0.3809.126 (d80a294506b4c9d18015e755cee48f953ddc3f2f-refs/branch-heads/3809@{#1024})"},"message":"ChromeDriver ready for new sessions.","os":{"arch":"x86_64","name":"Mac OS X","version":"10.16.0"},"ready":true}}
[Chromedriver@dec8] Starting W3C Chromedriver session with capabilities: {
[Chromedriver@dec8]   "capabilities": {
[Chromedriver@dec8]     "alwaysMatch": {
[Chromedriver@dec8]       "goog:chromeOptions": {
[Chromedriver@dec8]         "debuggerAddress": "127.0.0.1:59877"
[Chromedriver@dec8]       },
[Chromedriver@dec8]       "goog:loggingPrefs": {
[Chromedriver@dec8]         "browser": "ALL"
[Chromedriver@dec8]       }
[Chromedriver@dec8]     }
[Chromedriver@dec8]   }
[Chromedriver@dec8] }
[debug] [Chromedriver@dec8] Matched '/session' to command name 'createSession'
[debug] [Chromedriver@dec8] Proxying [POST /session] to [POST http://127.0.0.1:59882/session] with body: {"capabilities":{"alwaysMatch":{"goog:chromeOptions":{"debuggerAddress":"127.0.0.1:59877"},"goog:loggingPrefs":{"browser":"ALL"}}}}
[debug] [Chromedriver@dec8] Webview version: 'Chrome/76.0.3809.146'
[debug] [Chromedriver@dec8] Got response with status 200: {"value":{"capabilities":{"acceptInsecureCerts":false,"browserName":"chrome","browserVersion":"76.0.3809.146","chrome":{"chromedriverVersion":"76.0.3809.126 (d80a294506b4c9d18015e755cee48f953ddc3f2f-refs/branch-heads/3809@{#1024})"},"goog:chromeOptions":{"debuggerAddress":"127.0.0.1:59877"},"pageLoadStrategy":"normal","platformName":"","proxy":{},"setWindowRect":false,"strictFileInteractability":false,"timeouts":{"implicit":0,"pageLoad":300000,"script":30000},"unhandledPromptBehavior":"dismiss and notify"},"sessionId":"82edac5b762e74677d7eb2db694cf944"}}
[Chromedriver@dec8] Determined the downstream protocol as 'W3C'
[debug] [Chromedriver@dec8 (82edac5b)] Changed state to 'online'
[TizenTVDriver] Waiting for app launch to take effect
[TizenTVDriver] Clearing app local storage & reloading...
[debug] [Chromedriver@dec8 (82edac5b)] Matched '/execute/sync' to command name 'execute'
[debug] [Chromedriver@dec8 (82edac5b)] Did not know how to rewrite the original URL '/execute/sync' for W3C protocol
[debug] [Chromedriver@dec8 (82edac5b)] Proxying [POST /execute/sync] to [POST http://127.0.0.1:59882/session/82edac5b762e74677d7eb2db694cf944/execute/sync] with body: {"script":"return (() => {\n    window.localStorage.clear();\n    window.location.reload();\n  }).apply(null, arguments)","args":[]}
[debug] [Chromedriver@dec8 (82edac5b)] Got response with status 200: {"value":null}
[TizenTVDriver] Waiting for app launch to take effect again post-reload
[AppiumDriver@75c4] New TizenTVDriver session created successfully, session d77bbeed-80bb-42fd-8a44-c81862518e20 added to master session list
[debug] [AppiumDriver@75c4] Event 'newSessionStarted' logged at 1673281214774 (16:20:14 GMT+0000 (Greenwich Mean Time))
[debug] [TizenTVDriver@e834 (d77bbeed)] Cached the protocol value 'W3C' for the new session d77bbeed-80bb-42fd-8a44-c81862518e20
[debug] [TizenTVDriver@e834 (d77bbeed)] Responding to client with driver.createSession() result: {"capabilities":{"appLaunchCooldown":3000,"rcMode":"js","platformName":"TizenTV","automationName":"TizenTV","deviceName":"172.16.101.198:26101","chromedriverExecutable":"/Users/x/Projects/AppiumTizen/chromedriver76/chromedriver","appPackage":"wCC7ZHRYCs.demoApp","rcToken":"92501415","resetRcToken":true,"rcDebugLog":true,"rcKeypressCooldown":750,"newCommandTimeout":3600,"connectHardwareKeyboard":true,"deviceAddress":"172.16.101.198","udid":"172.16.101.198:26101"}}
[HTTP] <-- POST /wd/hub/session 200 12619 ms - 539
[HTTP] 
[HTTP] --> GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/screenshot
[HTTP] {}
[TizenTVDriver@e834 (d77bbeed)] Driver proxy active, passing request on via HTTP proxy
[debug] [Chromedriver@dec8 (82edac5b)] Matched '/wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/screenshot' to command name 'getScreenshot'
[debug] [Chromedriver@dec8 (82edac5b)] Proxying [GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/screenshot] to [GET http://127.0.0.1:59882/session/82edac5b762e74677d7eb2db694cf944/screenshot] with no body
[HTTP] --> GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/timeouts
[HTTP] {}
[TizenTVDriver@e834 (d77bbeed)] Driver proxy active, passing request on via HTTP proxy
[HTTP] --> GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/timeouts
[HTTP] {}
[TizenTVDriver@e834 (d77bbeed)] Driver proxy active, passing request on via HTTP proxy
[HTTP] --> GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/timeouts
[HTTP] {}
[TizenTVDriver@e834 (d77bbeed)] Driver proxy active, passing request on via HTTP proxy
[HTTP] --> GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/timeouts
[HTTP] {}
[TizenTVDriver@e834 (d77bbeed)] Driver proxy active, passing request on via HTTP proxy
[HTTP] --> GET /wd/hub/session/d77bbeed-80bb-42fd-8a44-c81862518e20/timeouts
[HTTP] {}
[TizenTVDriver@e834 (d77bbeed)] Driver proxy active, passing request on via HTTP proxy

[Setup] Error when trying to get a token

Hi team,

I'm facing a problem on the step :
appium driver run tizentv pair-remote

I wasn't able to get the token and the following error was triggered.

RMS@RMS-MacBook-Pro tizen % sdb devices                                           
List of devices attached 
10.0.0.43:26101         device          HG49EJ690U
RMS@RMS-MacBook-Pro tizen % sdb connect 10.0.0.43                                 
10.0.0.43:26101 is already connected
RMS@RMS-MacBook-Pro tizen % appium driver run tizentv pair-remote --host 10.0.0.43
[STDERR] 
[STDERR] /Users/RMS/.appium/node_modules/appium-tizen-tv-driver/node_modules/@headspinio/tizen-remote/lib/tizen-remote.js:795
[STDERR]       throw new Error(`Could not get token; server responded with: ${format('%O', res)}`);
[STDERR]             ^
[STDERR] Error: Could not get token; server responded with: {
[STDERR]   data: { clients: [ [Object] ], id: '555ae14d-bc28-419c-9d21-576c53c016f8' },
[STDERR]   event: 'ms.channel.connect'
[STDERR] }
[STDERR]     at TizenRemote.getToken (/Users/RMS/.appium/node_modules/appium-tizen-tv-driver/node_modules/@headspinio/tizen-remote/lib/tizen-remote.js:795:13)
[STDERR]     at processTicksAndRejections (node:internal/process/task_queues:95:5)
[STDERR]     at pairRemote (/Users/RMS/.appium/node_modules/appium-tizen-tv-driver/lib/rc-pair.js:14:19)
[STDERR]     at main (/Users/RMS/.appium/node_modules/appium-tizen-tv-driver/lib/rc-pair.js:68:5)
✖ Encountered an error when running 'pair-remote': Process ended with exitcode 1 (cmd: '/usr/local/bin/node ./build/lib/rc-pair.js --host 10.0.0.43')
RMS@RMS-MacBook-Pro tizen % 

Appium Version: 2.0.0-beta.46

Can you please help me ?

sdb shell 0 debug fails on TizenTV 2017

Problem

command sdb shell 0 debug works on Tizen 5.5 (TizenTV 2020) but fails for Tizen 3.0 (TizenTV 2017) with same wgt
2020
image
2017
image

sdb capability
image

the install/uninstall command is fine. Is it possible to skip debug command

appium server log

�[38;5;16m[AppiumDriver@60fb]�[0m Appium v2.5.1 creating new TizenTVDriver (v0.10.0) session
�[38;5;16m[AppiumDriver@60fb]�[0m Checking BaseDriver versions for Appium and TizenTVDriver
�[38;5;16m[AppiumDriver@60fb]�[0m Appium's BaseDriver version is 9.5.2
�[38;5;16m[AppiumDriver@60fb]�[0m TizenTVDriver's BaseDriver version is 8.7.3
�[38;5;16m[AppiumDriver@60fb]�[0m Explicitly enabling use of insecure features:
�[38;5;16m[AppiumDriver@60fb]�[0m chromedriver_autodownload
�[38;5;32m[TizenTVDriver@e01f]�[0m Creating session with W3C capabilities: {
�[38;5;32m[TizenTVDriver@e01f]�[0m "alwaysMatch": {
�[38;5;32m[TizenTVDriver@e01f]�[0m "platformName": "TizenTV",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:deviceAddress": "192.168.10.181:26101",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:udid": "192.168.10.181:26101",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:automationName": "TizenTV",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:rcMode": "remote",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:chromedriverExecutableDir": "/Users/jiyvn/aviu/apps/tv/chromedriver/",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:appPackage": "TXSXgdzhCp.Viu",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:deviceName": "Tizen3.0 2020",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:noReset": false,
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:app": "/Users/jiyvn/aviu/apps/Viu_dev.wgt",
�[38;5;32m[TizenTVDriver@e01f]�[0m "appium:rcToken": "15773870"
�[38;5;32m[TizenTVDriver@e01f]�[0m },
�[38;5;32m[TizenTVDriver@e01f]�[0m "firstMatch": [
�[38;5;32m[TizenTVDriver@e01f]�[0m {}
�[38;5;32m[TizenTVDriver@e01f]�[0m ]
�[38;5;32m[TizenTVDriver@e01f]�[0m }
�[38;5;32m[TizenTVDriver@e01f (012ab4c6)]�[0m Session created with session id: 012ab4c6-e55d-43d7-b6fe-ddd7de58928f
�[38;5;48m[TizenTVDriver]�[0m Received rcKeypressCooldown of type undefined
�[38;5;48m[TizenTVDriver]�[0m Uninstalling tizen app 'TXSXgdzhCp.Viu' on device '192.168.10.181:26101'
�[38;5;48m[TizenTVDriver]�[0m Running command: /Users/jiyvn/tizen-studio/tools/ide/bin/tizen uninstall -p TXSXgdzhCp.Viu -s 192.168.10.181:26101
�[38;5;48m[TizenTVDriver]�[0m Installing tizen app '/Users/jiyvn/aviu/apps/Viu_dev.wgt' on device '192.168.10.181:26101'
�[38;5;48m[TizenTVDriver]�[0m Running command: /Users/jiyvn/tizen-studio/tools/ide/bin/tizen install -n /Users/jiyvn/aviu/apps/Viu_dev.wgt -s 192.168.10.181:26101
�[38;5;48m[TizenTVDriver]�[0m Listing apps installed on '192.168.10.181:26101'
�[38;5;48m[TizenTVDriver]�[0m Running command: /Users/jiyvn/tizen-studio/tools/sdb -s 192.168.10.181:26101 shell 0 applist
�[38;5;48m[TizenTVDriver]�[0m There are 152 apps installed
�[38;5;48m[TizenTVDriver]�[0m Starting TXSXgdzhCp.Viu in debug mode on 192.168.10.181:26101
�[38;5;48m[TizenTVDriver]�[0m Running command: /Users/jiyvn/tizen-studio/tools/sdb -s 192.168.10.181:26101 shell 0 debug TXSXgdzhCp.Viu
�[38;5;48m[TizenTVDriver]�[0m Cleaning up any ports which have been forwarded
�[38;5;16m[AppiumDriver@60fb]�[0m Event 'newSessionStarted' logged at 1710915243869 (14:14:03 GMT+0800 (China Standard Time))
�[38;5;16m[AppiumDriver@60fb]�[0m Encountered internal error running command: Command '/Users/jiyvn/tizen-studio/tools/sdb -s 192.168.10.181:26101 shell 0 debug TXSXgdzhCp.Viu' exited with code 1. Stdout was: ''. Stderr was: 'closed '
�[38;5;16m[AppiumDriver@60fb]�[0m Error: Command '/Users/jiyvn/tizen-studio/tools/sdb -s 192.168.10.181:26101 shell 0 debug TXSXgdzhCp.Viu' exited with code 1
�[38;5;16m[AppiumDriver@60fb]�[0m at ChildProcess. (/Users/jiyvn/.appium/node_modules/appium-tizen-tv-driver/node_modules/teen_process/lib/exec.js:128:19)
�[38;5;16m[AppiumDriver@60fb]�[0m at ChildProcess.emit (node:events:518:28)
�[38;5;16m[AppiumDriver@60fb]�[0m at maybeClose (node:internal/child_process:1105:16)
�[38;5;16m[AppiumDriver@60fb]�[0m at Process.ChildProcess._handle.onexit (node:internal/child_process:305:5)
�[38;5;0m[HTTP]�[0m �[37m<-- POST /session �[39m�[31m500�[39m �[90m15122 ms - 876�[39m
�[38;5;0m[HTTP]�[0m �[90m�[39m

the app should be debuggable as using the same wgt
https://github.com/headspinio/appium-tizen-tv-driver/blob/main/packages/appium-tizen-tv-driver/README.md#troubleshooting

A similar issue was reported before in repo Samsung/appium-tizen-driver, so that's why I report here
Samsung/appium-tizen-driver#10

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (:sematicCommits). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

enable autodownlaod capability

I wondered if

this.#chromedriver = new Chromedriver({
// @ts-ignore bad types
port: await getPort(),
executable,
});

can have executableDir: opts.chromedriverExecutableDir and isAutodownloadEnabled: isChromedriverAutodownloadEnabled.bind(this)() to enable autodownload in addition to explicit driver path only.

https://github.com/appium/appium-android-driver/blob/4bead422c2f36e8a019073b6acba0853ba9b40e4/lib/commands/context/helpers.js#L712C1-L728C6

Then, the executable or chromedriverExecutableDir should be required, but not both.

As same as the Android, the autodownload should be behind the same security flag.

Error in starting appium session onTizen OS

I am trying to execute the following code

const wdio = require("webdriverio");

const opts = {
// path: '/wd/hub',
port: 4723,
capabilities: {
"platformName": "TizenTV",
"appium:automationName" : "TizenTV",
"appium:deviceName" : "172.31.42.205:26101",
"appium:chromedriverExecutable" : "/Users/kushagravarade/Downloads/chromedriver",
"appium:rcToken" : "16085789",
"appium:appPackage" : "org.tizen.example.MovieLibrary"
}
};

async function main () {
const client = await wdio.remote(opts);
console.log("I got client as: " , client)
// await client.deleteSession();
}

main();

and I am getting the error when running the code. I am attaching error log and also appium log. Can you please help me with this issue.

appium.log
err.log

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.