These modern activities (UiAutomation.Activities 21.4.4) still don’t handle variables well.
I have a Use Application/Browser that doesn’t use selectors, it uses Input Element:
Therefore the embedded Check App State shouldn’t need a Window Selector, it should inherit from Use Application/Browser. But when I try to edit target:
I’m not saying it doesn’t work, I’m saying it shouldn’t require a Window Selector because the window is passed as a variable. But it still requires Window Selector. No idea what would happen if the window selector were incorrect, if it’s just ignore.
Could you maybe clarify how do you extract the input element that you pass as a variable?
The design time selector editing experience makes sense, because the variable is not set at the time, but I am wondering what this GetWindowSelectorTags not implemented for tag 'webctrl' is all about. Where does it show this error?
I can see that the internal issue that was tracking this topic was marked as completed in 22.10. Therefore, upgrading UIAutomation package to 22.10 should solve the issue.
Hi Paul,
Did you ever find a fix for this? I just ran into this same issue with my project. We pass the browser through io argument throughout process but I can’t get this checkappstate to work with that.
Thanks,
Joshua
No. The only way I’ve been able to modify an activity that’s showing this error is to add a Use Application/Browser, indicate the window, then copy the activity into it, make the selector changes, then copy it back to the Use Application/Browser that has the input element.
What’s weird is it doesn’t always do this, maybe it depends on which app you’re working in - but I haven’t found any pattern.