Can't Spy Elements with Google Chrome

[ZacharyFelts]

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
------------------------------

[NileshJadhavBP]

Hi Mayank,

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

Thanks
Nilesh

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

[MayankGoyal2]

@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
------------------------------

[NileshJadhavBP]

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
------------------------------

[MayankGoyal2]

@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
------------------------------

[peterlacken]

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
------------------------------

[CharlieSimmon]

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

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

[EstebanMontesi1]

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

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

[SulemanRathor]

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
------------------------------