When I use the “Use Application” activity to open a website in Edge, UiPath is unable to interact with the site. I’ve tested it using a simple workflow that makes a search on google and get a timeout when the robot tries to type into the search field on google.com. This only happens if UiPath opens the browser window, if I manually move focus to the window UiPath can interact with the website just fine. It seems to somehow be related to the Chromium Input mode but I’m not entirely sure. If I instead use the “Simulate” input mode, UiPath will bring the window into the foreground but sometimes the edge window will not have rendered, showing just a blank page (However with the correct URL).
Its problematic as it makes developing workflows that opens a browser tedious. I have to add a delay after opening the page such that I manually have a chance to click on the browser window so that UiPath can interact with it.
I’m really at a loss here, any ideas?
Steps to reproduce:
Configure “Use Application” to open www.google.com in a Edge browser using chromium input mode.
Configure “Type into” to type into the search bar, I am not sure if the builtin verification is necessary for the issue to appear
Configure “Click” to click on the “Google Search” button to perform the search.
If UiPath is responsible for opening the Edge browser, I get a timeout on step 2 until I have manually moved focus to the browser instance once. I would upload an example project but can’t since I am a new user.
Hey @Hjorth have you enable the edge extension. so UiPath will interact with The repected browser for eq- yiu are working with edge so your edge installed or enable the Extension.
open UiPath studio → go to Tools section->UiPath Extension->enable Edge extension
Hi thanks for helping out.
I am using the latest package version 24.10.11 for UiPath.UIAutomation.Activities.
The Edge extension is installed and I have no problem interacting with webpages once Edge has received “focus” at least once. What’s weird is that if I add a “Click” using the Hardware input mode, the browser window is brought to the front but without the page rendered and the robot cant interact with the page. If I manually click the browser window, the page renders and then the robot can interact. Its all quite confusing.
Just tested the workflow I described above using Chrome and it works flawlessly so I has to have something to do with the Edge Chromium integration. Unfortunately our robots run on Edge so switching to Chrome is not an option.