Any news on this? I keep getting this bug over and over again. It makes Kantu/UI.Vision unusable. If I cannot rely on the TEST software working properly, it is of no use. It just seems to happen at random intervals. Occasionally, I can get all the way through a test-suite, but most of the time, at some point, this rears it’s ugly head, so to speak. Unfortunately I cannot demo with the website I’m working on as it contains confidential information / GDPR. Other information: I only ever have one tab open in a single browser (Chrome) and that’s it. Last few lines of log this time around are as follows:
[info] Executing: | while_v2 | {TitleText}!={ScreenToGoto} | | [info] Executing: | click | xpath=//*[@id=“PriMsgPanel”]/div[1]/div[2] | | [error] Error #101: UI.Vision RPA is not connected to a browser tab
In my opinion this bug is random and it’s present from 1 year.
There is not any solution to solve because Katalon and selenium have the same bug and selenium is the base of Ui vision.
For securety reason i run a macro, after i close firefox and reopen before run another macro to limit the “Error #101: Kantu is not connected to a browser tab” bug because it is random and it ìs present in all version of Ui vision.
I seach a solution from 1 year a this bug and there are nothing to do.
Hi newuserkantu. This is NOT good news!! ha ha! Unfortunately I cannot close the browser and re-open it between tests as it’s one long test - a sequence of events. E.G. Log in, create in form, add lines to form, post form, export data that form generates into file to be uploaded, upload file and post, then repeat and not necessarily in the same sequence/order each time. Closing the browser and the logging back in would be so time-prohibitive, it’s not viable and even if it were, it’s not possible with the website I’m working with as it needs an active session throughout the entire process.
Kantu / ui.vision is not a stable/viable product. I’m going to have to start looking elsewhere, I think.
If you’re right, then I find myself thinking “How can a piece of software have a fundamental bug like this and not do anything about it for a year?”
There is little point adding new features, etc, if the main functionality doesn’t work properly.
Currently, this product is literally unusable.
I am now getting “empty stack” and “Can’t find monitor target with id ‘number.number’”
I worked from 10 years with imacros for firefox 56 and working well, never show this problem, after firefox migrate to new engine Quantum all old macro recorder need to rewrited in new code and there are many incompatibility.
Here some old post with the bug “Error #101: Kantu is not connected to a browser tab” read the date, i tried all ui vision version and sometimes show this error.
[Apr 16]
[Nov 18]
[Jan 4]
[Apr 4]
And more and more
In my opinion after 2 years with this error i think never will be fixed.
I started macro from blank firefox page so this error was expected. I switched to “normal” page (tab) during macro execution. And I was expecting that kantu will connect to a browser tab. Which did not happen It seems kantu does not even try to “catch” the new context.
Can something be done? And is there some good alternative (if not)? Except for iMacros which is no way as well now.
I am getting 101 in this case also. Kantu is not capable to connect to browser tab for waitForPageToLoad…
If I leave pause command it is problematic as well. I cannot remember if it gives same or other error though.
I should add that this is not happening always. Command waitForPageToLoad might be executed correctly.
I really miss good old iMacros (with javascript scripting interface) where such problems were very rare.
I have used imacros on firefox 56 for 10 years and as established it is better than ui vision, Imacros never crashes and works without problems all day long but it has limits in the commands.
Ui vision is a good program but it has defects that have never been resolved which create a lot of discomfort for those who automate because when you automate you need the software to work perfectly. The problem of multiple tabs that open with execution of the “selectWindow” command I solved it using firefox ESR 60 and ui vision 5.1.9 it never happened with that version of firefox while it often happened to me with other versions of firefox and with others ui vision versions.
About the problem “Error # 101: Kantu is not connected to a browser tab” is an error also present in Katalon Recorder and in selenium therefore I believe that it is the basic structure of ui vision to have it and I believe that it can never be solved.
To reduce the possibility that this error occurs, I use of batch files that periodically close and reopen firefox, when the error “Error # 101: Kantu is not connected to a browser tab” occurs, you must necessarily close the browser and reopen it otherwise from at that moment no macros will work because ui vision has lost control of the tabs for this I plan periodic shutdowns of firefox to prevent this problem.
An alternative solution at “Error # 101: Kantu is not connected to a browser tab” is in the ui vision windows “Table View” select a line with a command and click “Info for this command” it open a new tab from ui vision windows and restores control of the tabs.
I love ui vision but is very hard automate with this random bug.
In my opinion after 2 years with this error i think never will be fixed.
The error #101 is somewhat of a “catch all” error for several different communication problems between extension and browser. Many of these issues have been solved by now. Maybe some other problem still show up for you, and we would love to fix it, too. But we need a test case for it:
@jathri@newuserkantuWe need a test case that we can run, than we can recreate and fix this error. You (or anyone else with this issue!) can also email me at team AT ui.vision and mention this forum post. Then we can give you remote access to one of our test systems (Windows, Mac or Ubuntu) and you can log in and try to recreate the error there.
Can you add option to enable debug (or other very thorough) level of logging? So we can export a proper log and send it to you to isolate the issue(s)?
I got this error message and various others.
I tried lot of solutions but did not helped.
And I try this: pause 1-3sec before and after the command what cause error , change the generated target to shorter one. //[@id=“pelda”]/div[2]/div/a[2]/h34 to this xpath=(//[text()=‘adatok’]).
This solved the errors for me. Tested 1h and 5 windows.
I think the error "Error # 101: Kantu is not connected to a browser tab” happens after a popup window is closed based on my experience (not sure if there are other cases though). Try downloading Chrome extension “Open link in same tab, pop-up as tab [Free]” (link:Open link in same tab, pop-up as tab [Free] - Chrome Web Store)
The extension will block popup window and open a new tab instead. I think this workaround will solve majority of "Error # 101: Kantu is not connected to a browser tab”
I’m getting less of this error lately, for some reason.
But is there any way for Kantu to re-connect to the browser window, given the fact it’s the only window opened?
Solved this by adding a wait for page to load on the 1st line of macro. This allowed time for the browser to open a tab before Kantu throws instructions at it. Hope it works for others too.