"uninitialized UI node" Have you seen it?

uiautomation

#1

“uninitialized UI node” Have you seen it ?


#2

I just saw this error for the first time. Did you find a solution?


#3

Here is a simple project that exhibits the issue.sample.zip (5.3 KB)


#4

I feel a little silly, but for the benefit of future readers, the problem appears to be with null objects. In the specific example I uploaded, there is a local variable hiding the workflow input argument (both are called appBrowser), but since the locally scoped appBrowser was never initialized, it’s null, and my “Navigate to” action throws the “uninitialized UI node” error. There are many ways to create the problem, such as implicit type casting that fails, variable hiding, and the list goes on. I hope someone finds this helpful in the future.


#5

Yeah, thank your for your advise. In my case I was trying to make a click into a context without being initializated, more especific, I was trying to attach a browser into a new secuence, but when I invoke the sequence I did not put the value, so the click didnt work. Good look.


#6

Hey,
I am encountering same problem,Can tell me how to fix it?


#7

Hey, you may have figured it out by now but I’ll still post in case anyone else comes across this problem.

So when you use the open browser activity you have the option to create a “Browser” type variable, simply create one here and then anytime you use another activity which is referencing the same browser (Such as ‘navigate to’) you can use this variable as an input.

Hope this is of some help to someone!