Issue
I've been developing an automation tool for our team using SeleniumBasic
that has worked FINE for over 2 years until very recently.
The scope of the tool is to navigate the MS Teams Web App
and provide simple interactions with multiple chat rooms throughout the evening (still using the Classic App
and not migrated to the new yet).
The problem I'm having is I receive the following errors when I try to switch to an iFrame
after moving from the main window. I never experienced this before, and it seems to have happened after Chrome was updated to version 120 - unsure how to make this antiquated software get around this.
Minimal code example:
If myChrome.IsElementPresent(FindBy.XPath("//iframe[starts-with(@id,'experience-container')]")) Then
myChrome.SwitchToFrame myChrome.FindElementByXPath("//iframe[starts-with(@id,'experience-container')]")
End If
The code has not changed at all, so what has, and what do I need to do to allow it to keep the User Account? I've never supplied anything as I've just navigated the existing elements within the frame and allowed the Teams Web App
to process it all.
Solution
When researching this error, I found many references to MASL
failing etc., but couldn't see where or how this was occurring. It appears with the updated versions of Chrome, there is a large difference in how Chrome itself is handling all the manipulation of the Teams Web App
and is now capable of detecting when the bot clicks on something vs the user.
The only way I could workaround this was by forcing the bot to open the URL to whichever portion of Teams I was trying to utilize (such as the Calendar) an then proceed from there.
It's a tad kludgy unfortunately, but it beats having to try and develop some way of getting MASL to work with VBA/SeleniumBasic
(I'll gladly accept an answer that has a way of solving this deeper need - must be Excel VBA
, using SeleniumBasic
- but for now, this works.)
Answered By - k1dfr0std
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.