After the latest update of ui.vision to version 6.3.2 none of my makros is running anymore… I run into this error when openin an URL via the open comman (the URL is accessable…):
pendingPlayingTab reset expired!
Seem like the ui.vision interface looses the the link to the browser instance startet…
Any hints?? It’s important as ui.vision is part of a more complex workflow…
Seems to be related to Chrome only. I am testing now with FirefoxPortable (latest release) and for now my tests are promisng… Just checked that easy script… Will rewrite the scripts now and see what’s happening
It was Windows, I had to revert to the September release and disable hardware acceleration in Chrome, I will see if I can repeat the issue on another machine
For me it’s on Windows Server 2019.
And NO - switching to Firefox does not solve my problem as I start the scripts from a batch file as a scheduled task. In this case Firefox has no GUI so the macro fail
Running the scripts as a scheduldes task with Chrome it works perfectly. So we need a solution. And yes - as fellcroft said -obviously RPA is not communication with Chrome…
I downgraded ad installed now UI.Vision V6.2.8 from the archive parallel to V6.3.2 and this works fine for me in chrome. But the question is… will this version be updated or does it remain installed and the new version 6.3.2 will be updated?
Sorry to say that Firefox does not work as it has no where RPA can place its commands (open website, enter username/passwd, do some clicks…). In chrome this all workes fine even when the user is not logged on…
I uploaded my video now but the screen is black… Are there any restrictions? It’s a small video (1444x900px), just some 300kb in size… But it works when you download the video
No worries, we will not update it. However, it will stop working January 17, 2023, because by this date Google disables all V2 manifest extensions. It is also possible that some Chrome update breaks it earlier.
That’s good news!! So having 6.2.8 installed parallel to 6.3.2 (with 6.3.2 disabled) should be a working workaround…
And maybe next version 6.3.3 or so will fix this issue with missing communication between RPA and Chrome