topic RE: Can't Spy Elements with Google Chrome in Product Forum

Can't Spy Elements with Google Chrome

ZacharyFelts — Fri, 30 Oct 2020 17:44:00 GMT

As the title says, I can't spy elements.

Google Chrome: V 86.0.4240.111
BluePrism: V 6.8.1
Extension: 2.1

------------------------------
Zachary Felts
------------------------------

RE: Can't Spy Elements with Google Chrome

NrupalJoshi — Fri, 30 Oct 2020 19:30:00 GMT

I have been having similar issues twice now but restarting the computer has helped. Not sure what the issue is.. I have 6.9 version

------------------------------
Rup Joshi
------------------------------

RE: Can't Spy Elements with Google Chrome

peterlacken — Sat, 31 Oct 2020 08:51:00 GMT

The problem is the default port that the Chrome extension uses is blocked - 31924. A restart of the machine is the short term fix but try in the settings to un-tick fixed port 31924. This issue is fixed as I understand in 6,9.

------------------------------
PeterLacken
Ren Røros Intelligent Automation
Peter.Lacken@rria.no
http://www.rria.no
------------------------------

RE: Can't Spy Elements with Google Chrome

ZacharyFelts — Mon, 02 Nov 2020 05:04:00 GMT

How do I go about un-ticking the fixed port 31924?

------------------------------
Zachary Felts
------------------------------

RE: Can't Spy Elements with Google Chrome

benny.poumoko-bafouatika — Mon, 02 Nov 2020 11:35:00 GMT

Within Blueprism GUI go to Settings and Under >>> System>>> Settings and scroll down to browser extension connectivity, after trying that if you are still not able to spy anything please raise a support ticket so that we can look at this issue further.

Kind Regards

------------------------------
Benny Poumoko-Bafouatika
Customer Support Analyst
Blueprism
------------------------------

RE: Can't Spy Elements with Google Chrome

ZacharyFelts — Mon, 02 Nov 2020 15:24:00 GMT

It appears it was already un-checked. I'll start a support ticket now.

------------------------------
Zachary Felts
------------------------------

RE: Can't Spy Elements with Google Chrome

NileshJadhavBP — Tue, 03 Nov 2020 00:17:00 GMT

Thanks @ Benny Poumoko-Bafouatika for sharing the ans with detail.

Thanks
Nilesh

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

RE: Can't Spy Elements with Google Chrome

MayankGoyal2 — Wed, 02 Dec 2020 21:55:00 GMT

@ZacharyFelts - Were you able to fix this issue? We are also facing similar issue and looking for some inputs to resolve it. Along with Browser mode i dont see option of accessibility mode as well in chrome.

I also referred chrome automation guide where it has some details on --force-renderer-accessibility. https://portal.blueprism.com/system/files/documents/v6.9%20User%20Guide%20-%20Native%20Chrome%2C%20Edge%2C%20and%20Firefox%20Integration_2.pdf. However this option is mentioned only for UIA mode.

When working with IE, it shows 5 modes (HTML, Window, UI, Accessibility, Region) but with chrome only 4 modes (HTML, Window, UI, Region)

------------------------------
Mayank Goyal
------------------------------

RE: Can't Spy Elements with Google Chrome

peterlacken — Thu, 03 Dec 2020 06:25:00 GMT

Hi,

what version of blue prism and chrome extension are you running? Be sure to check the chrome extension on the browser is compatible with the version of blue prism.

Do you have fixed port 31942 set in the settings? If so, try unticking that and using dynamic ports.

you always need to restart the machine after you get into the no spy on browser state. It is the only way to reset.

peter

------------------------------
PeterLacken
Ren Røros Intelligent Automation
Peter.Lacken@rria.no
http://www.rria.no
------------------------------

RE: Can't Spy Elements with Google Chrome

MayankGoyal2 — Thu, 03 Dec 2020 17:53:00 GMT

@peterlacken - We are running with BP 6.8.1 and chrome extension 2.1. I believe this is a compatible set.
The settings port checkbox is unchecked by default and we haven't changed it.

------------------------------
Mayank Goyal
------------------------------

RE: Can't Spy Elements with Google Chrome

NileshJadhavBP — Thu, 03 Dec 2020 18:00:00 GMT

Hi Mayank,

have you launch chrome using application modeler ? or using inbuilt VBO.?

Thanks
Nilesh

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

RE: Can't Spy Elements with Google Chrome

MayankGoyal2 — Thu, 03 Dec 2020 18:16:00 GMT

@Nilesh Jadhav - We invoke chrome both ways, with application modeller using launch and at times running chrome exe process with URL parameter. In all cases after launching we attach if not attached. URL is a dynamic value passed from process to object, so even if we have a value in app modeller that is overwritten, This all works in v 6.4 with extension 1.

With 6.8.1, everything till attach is working fine, but when i start spying in browser mode it is not detecting any element on webpage.

------------------------------
Mayank Goyal
------------------------------

RE: Can't Spy Elements with Google Chrome

NileshJadhavBP — Thu, 03 Dec 2020 18:30:00 GMT

Hi Mayank,

Restart your controller machine.

Create other object and try to launch chrome and try to spy it. (Pass your link in the application modeler)

*don't use attach page or action.

check its working or not....

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

RE: Can't Spy Elements with Google Chrome

MayankGoyal2 — Thu, 03 Dec 2020 18:39:00 GMT

@Nilesh Jadhav - We tried these steps -

1) Restarted the machine
2) Created a new VBO with URL in app modeller (google URL)
3) When launched, chrome was already attached, so no need to attach
4) Tried spying text box, but it was not identifying

I believe the solution most probably is the timeout value in config file as mentioned in this guide (Page 12) - https://portal.blueprism.com/system/files/documents/v6.8%20Data%20Sheet%20-%20Native%20Chrome%2C%20Edge%2C%20and%20Firefox%20Integration_2.pdf

However I have raised a support ticket to get concrete solution from BP team.

------------------------------
Mayank Goyal
------------------------------

RE: Can't Spy Elements with Google Chrome

peterlacken — Thu, 03 Dec 2020 20:03:00 GMT

Hi,

Blue Prism have done some major changes on the chrome extension between 6,8 (2.1) and 6,9 (2.2). 2.2 is much improved. I would advise to upgrade before developing extensively in chrome.

In 6,8, we have experienced spy problems when using Kill Process on chrome.exe. To close a browser we must sent a shortcut key event (CTRL-SHIFT-W)-this seems to exit gracefully and prevents spy issues.

we have recently upgraded to 6,9 and have found one more problem with detach logged under DT-185. I think the chrome extension is a work in progress and may not stabilize until v7.

good luck,

------------------------------
PeterLacken
Ren Røros Intelligent Automation
Peter.Lacken@rria.no
http://www.rria.no
------------------------------

RE: Can't Spy Elements with Google Chrome

CharlieSimmon — Fri, 04 Dec 2020 11:36:00 GMT

Not even close worked for a short bit after installing the trial version then everything started getting corrupt

------------------------------
Charlie Simmon
------------------------------

RE: Can't Spy Elements with Google Chrome

EstebanMontesi1 — Sun, 25 Apr 2021 23:43:00 GMT

Can't find this setting which tab are you using I can't seem to find this anywhere?

------------------------------
Esteban Montesinos
------------------------------

RE: Can't Spy Elements with Google Chrome

SulemanRathor — Fri, 01 Apr 2022 11:18:00 GMT

Hi All

I think I've worked it out.

This works with Blue Prism 6.10.1, not sure about your version but please try the below:

If MS Edge (maybe other browsers too, not tested) is running in the background the Chrome extension fails to spy web elements. The solution is to kill MS Edge (maybe other browsers too) to avoid the clash. You can use the environment object with the kill process > "msedge".

This will hopefully save everyone some time 🙂

Regards
Suleman

------------------------------
Suleman Rathor
------------------------------