Verification (verify) gets compiling error in 25.10.22 and above, C# project

Help Studio
1

Hello

I get error on verification regarding ui activities if i use verify. This is in C# bases project and only in later package version. Is there anyone out there that knows if this is a common issue or not? Does not matter what type of verification i use and as soon as i turn the function of it works flawlessly. No other errors when doing analyze on the project.

image
image862×277 49.9 KB

2

Hi @Ninjabullen

Can you try and remove the quotes around your text and recreate them?
Often when text is copied eg. from a website, the “wrong” quotes are used.
Is is not apparent visible, but they do differ.

Regards
Soren

3

I was a bit fast on adding this forum post, my bad. After tinkering a bit it started working. It was very strange, both my click in login and type into username had the same error for many debug runs.

Suddenly it started working.

4

Hi @Ninjabullen

This is a known issue with newer UIAutomation packages in C# projects. The Verify feature still tries to use VB expressions, which causes the compilation error. Execution works fine once Verify is turned off. For now, the workaround is to disable Verify, downgrade the UIAutomation package, or use a VB project if you really need verification.

5

Hi @Ninjabullen

Try to downgrade UiPath.Testing.Activities to 25.10.21 or 24.10.x and align package versions. Might be the VBValue error appears because VB expressions exist in a C# project. Just replace VB syntax with C#, disable - Allow VB expressions,and rebuild.

Happy Automation

6

The solution for me ,without downgrading the package, is to have for example the

Example - Type into

  1. Leave input field in blank when changing in the dropdown to verify
  2. Add the value to be verified
  3. Add the value to input

If i do this in the order above the bug never shows. It is only (sometimes) when i have a value already, change in the dropdown to verify text and try to run the process that i get the bug mentioned in the first post.

Related to the bug mentioned in the first post. When exporting the sequence/flow using the “Export as Workflow” to its own xaml file, and it has verify text parts, it sometimes makes the whole/new xaml file with errors. The error says that the file uses declaration of both VB and C# in the same xaml file, even when this is not the case (the process cannot run, cannot save the xaml after editing or anything). To resolve this (even if its a seperate issue. When the issue occurrs saving the xaml file does not work) i copy paste all activities to a new xaml file and the usually resolves the issue.