Hi Team I need to connect Mobile device using BrowserStack but I'm getting request could not be found

[Mada_Sai_Krishna]

Hello Team,

I’m trying to connect mobile device using browserStack but I’m getting the request resource could not be found

please find the attached screenshots for your reference

Please help me on that

Regards
Saikrishna

[lrtetala (Lakshman Reddy)]

Hi @Mada_Sai_Krishna

Check on below post

UIPath with BrowserStack

Hi all Is there anyone success to connect the simulator of BrowserStack, Please tell the new method to connect the devices. I have learn from the video :Mobile Automation in Uipath with BrowserStack | UiPath Test Suite Mobile Automation | RPA Uipath - YouTube, but I found that information is too old that I can get the the app value of capability [图片] [图片]

Regards,

[Mada_Sai_Krishna]

Hello @lrtetala ,

I have already watch that video that is older version of BrowserStack but I need new version of Browserstack.

if you know please help me on that.

Reagrds,
Saikrishna

[phaserescu (Cristian Bidea)]

The appium url refers to a local address. I don’t think this is right! What I think is happening is that you have a local instance of Appium running and that instance doesn’t recognize one of the options passed.

[lrtetala (Lakshman Reddy)]

@Mada_Sai_Krishna

Please go through this docs

Test Suite - Troubleshooting scenarios

Mobile Automation : Not able to Communicate with Browser Screen on Mobile App

This is expected! Unless you start the session with a web app the webview context will not be debuggable (hybrid apps are supported though if the webview is set to debuggable from the app). Taking this into consideration, a work around is to start the session with a web app and then manually start your application. Hopefully when a link opens it will open in the chrome that has a debuggable webview and afterwards you can switch back and forth between your app and chrome using the Manage Other Ap…

Hope this helps!!

[Sachin_Chikodi]

The issue seems to be with connecting a mobile device through BrowserStack, resulting in a “request could not be found” error. This might be due to an incorrect URL or endpoint setup for the device on BrowserStack or a potential connectivity problem. Double-check the configurations and network connection, or seek assistance from BrowserStack support for further troubleshooting.