03-05-21 04:10 PM
Hi all,
I'm using BP version 6.10.1 which supports edge chromium but I'm not able to use it for spying. When try to attach to already running browser instance it attaches without a problem but BP doesn't identity any elements on the webpage and only the outer window get recognised by BP and if I launch the edge browser through BP, it is able to identify elements of the webpage but only in browser mode and not in any other mode like UIA. Ive the edge extension installed and enabled. Please help!
03-05-21 06:39 PM
ID | BP-3553 |
Introduced in | Blue Prism version 6.8 |
Status | Confirmed – Will be addressed in Blue Prism 6.11. |
Issue | When launching an Edge browser via the Application Modeller, the browser launches but Blue Prism cannot connect to it to spy the elements. If the user then attempts to launch Edge again via the still active Launch button in the Application Modeller (if the initial browser window remains open), Blue Prism connects and spies the elements successfully in a second browser window. The issue has been found in versions 86 and 89, but we expect it to be present in all currently available versions from 86 onwards. |
Workaround | N/A |
04-05-21 08:00 AM
04-05-21 01:45 PM
11-06-21 11:03 AM
Hi,
I am having similar issues. Upgraded to 6.10.1 in order to use Browser mode to spy an application i Edge Cromium (former IE), and used the BLP Conversion tool on my old object.
I can launch the application in Edge Cromium, and apparently attach to it, but when I try to spy an element using browser mode, nothing is selectable.
Using the other spymodes, I can select some elements. However I would really rather not use UI since it is sooo slow.
We have checked Use Fixed browser extension port (31924) only, and have BluePrism browser extension 6.10.1 activated.
Plese let me know what I can do ...
11-06-21 02:59 PM
01-07-21 04:49 PM
25-08-21 11:23 AM
Hi Ingrid,
I am not sure are we posting solution for the initial problem, but I would like to point out one thing after updating to V7.0. Browser extension was completely useless after update. Attaching freezes, errors were like "No browser extension found", "AMI error occured" and everything between.
Now I have noticed, that every MSEdge object might or might not have following "repairable" errors / Advices after the updates: (Check errors from Object)
This helped us a bit. At least old (developed in V6.8 platform) processes are now running!
Br, Mikko
25-08-21 11:35 AM
Hi Mikko,
Thanks for your info, and Yes Repair Errors function is good, but, at least for us, it doesnt help with the Server Extension error... and what is even worse, it seems that BlueP rism spying actually starts not-working 100% some time before the Server extension error comes up,. so it can suddenly not spy elements that were 'spyable' a while ago, but some elements it can still find... so it is har to see if it is working or not..., and then a bit later the server extension error comes... such a waste of time finding out what is wrong, restarting PCs etc...
And we did not have any Edge objects prior to the upgrade, so we have migrated from IE to Edge after the upgrade to BLP 7.0
I really hope that BluePrism soon finds a solution to this issue...
Best regards
Ingrid
26-08-21 06:51 PM