You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi team,
I'm observing that ListensToLogcatMessages.startLogcatBroadcast(String host, int port); hardcodes inside the WS protocol.
endpointUri = new URI(String.format("ws://%s:%s/ws/session/%s/appium/device/logcat", host, port, ((RemoteWebDriver)this).getSessionId()));
For some purposes I use Appium environment remotely by HTTPS.
So, in this case connection is refusing by Appium server because I should use WSS instead.
I merely copy-pasted the method implementation to my project and changed WS to WSS and it works!
Please review the possibility to extend the client implementation to support WSS as well
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi team,
I'm observing that ListensToLogcatMessages.startLogcatBroadcast(String host, int port); hardcodes inside the WS protocol.
endpointUri = new URI(String.format("ws://%s:%s/ws/session/%s/appium/device/logcat", host, port, ((RemoteWebDriver)this).getSessionId()));
For some purposes I use Appium environment remotely by HTTPS.
So, in this case connection is refusing by Appium server because I should use WSS instead.
I merely copy-pasted the method implementation to my project and changed WS to WSS and it works!
Please review the possibility to extend the client implementation to support WSS as well
Thanks, M
Beta Was this translation helpful? Give feedback.
All reactions