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 App activity.

  1. In the video I’m starting the session with a web app, and clicking around to show that is debuggable
  2. Then manually install my apk
  3. Using Manage Other App to start my App
  4. Click around
  5. Going back to Chrome
2 Likes