Open semeguze opened 2 weeks ago
Hi @semeguze, could you please confirm if the ODC server injected into your application by the driver is functioning correctly?
Check the Roku BrightScript logs while performing the steps mentioned:
nc <device-ip> 8085
📝 This may reveal app instrumentation issues.
After installing and running the application using Automation/Inspector + Roku Driver, execute the following requests:
# Outputs are not needed, requests are necessary
# to verify whether they reach the server and if it can respond.
curl http://<device-ip>:8061/registry # Registry state
curl http://<device-ip>:8061/app-ui # XML Page source
📝 This will indicate if the ODC server launches with the app and whether the issue pertains to the page source retrieving or the entire server. Please review BrightScript logs during these requests as well.
Issue Summary
I’m encountering an internal error when running a command with the RokuDriver and the ODC context. The error message indicates a
TypeError: fetch failed.
I'm using the most updated Node + Appium + Appium inspector versions.
Context and Additional Information
We are trying to use the ODC context instead of ECP because our team is attempting to add custom arguments to the DOM file, such as the
automationID
. However, we are not able to view the automationID argument while reading the DOM file with the default configuration.Capabilities used:
Steps to Reproduce
TypeError: fetch failed.
The session is starting using the Appium Inspector, and the App is installed in my Roku device, but the page source it's not loading:
What did I already try?
I already tried:
npm install node-fetch
both locally and globally without successSystem info
Logs
These are the logs from the
appium
server:Any help would be really appreciated!! Thanks! 🚀