09-06-23 07:56 AM
Hi All,
Unable to spy the elements in blue prism browser mode using chrome. Please assist with the same. Thank You.
Below are the version details.
Blueprism version: 6.7
Chrome version: 114.0.5735.110
Blueprism Browser Extension: 2.1.0
09-06-23 07:59 AM
What is the error that you are getting?
Check the browser extension compatibility here
09-06-23 09:08 AM
There is no error persisting. I'm unable to spy any element through browser mode in chrome and unable to highlight the any existing element which was already there in application modeler. although I'm using right versions of extensions.
09-06-23 09:49 AM
You can restart your system or blueprism logout and login can check still issue is coming or not.
You can open blueprism application as admin and check.
Thanks,
Jagadish
09-06-23 10:03 AM
Terminating chrome properly after processing. As a workaround, you can restart the machine.
If above didn't work, then check enabling 'Use Fixed browser extension port'
09-06-23 01:33 PM
Hi Laxman,
It sounds like you might not be properly attached. If you roll through the various spy methods, are you able to identify anything in Win32 or UIA? I've found that if UIA is the only thing that works well, usually that means I'm not really attached.
Chrome opens multiple processes with each new tab. I would check your attach stage to make sure you're attached to "chrome" process with a valid window title. If that doesn't fix it, try child index 0 or 1. For development purposes, if possible, try to have only one Chrome window and one Chrome tab open while spying elements (I know it's not always possible). If you still can't spy/highlight correctly and you've tried all of this and the other suggestions (reboot, etc.) you can try attaching via PID. It's a bit of a pain to do it, but there is an action for "read memory stats" in the environment utility. You pass in the "Chrome" process name and it will return a collection of process names and PIDs. PID is a valid input on the attach stage. You loop through the PIDs, attaching to each one, waiting for a valid element on the screen, the detaching if it's not found. Be careful to never attach to the PID = 0 (Idle Process). It'll lock up BP and you'll have to kill it.
Good luck and hope this helps!
12-06-23 05:42 AM
Hi Laxman,
There are two scenarios.