UiPath.UIAutomation.Activities v21.10.3 - strange problems after upgrading from 21.4.4

Hi, after upgrading to v 21.10.3 of the UiPath.UIAuotamtion.Activities I am experiencing all kinds of strange errors. The biggest problem is that no errors are shown in Studio, but when I try to run an activitiy I get errors. Example is when I try to call the NewRow() method of an DataTable (I’m using C#).

System.Data.DataRow MyDataRow = MyDataTable.NewRow()

This looks fine in Studio, but when executing the following error is thrown:

Cannot implicitly convert type 'object' to 'System.Data.DataRow'. An explicit conversion exists (are you missing a cast?)

This used to work fine before. What has changed? The previous version of the mentioned package I used was 21.4.4.

My Studio version:

Studio Pro 2020.10.4 - 1/26/2021
Enterprise License
Windows Installer

License Provider: Orchestrator
Activation ID:

Microsoft Windows Server 2016 Datacenter 64-bit
.NET Framework Version 4.6.2

The UiPath Studio version should be sufficient for this package according to description (20.10 or higher).

I tried to downgrade to 21.4.4, but this now completly breaks my activity.

EDIT: I managed do downgrade to 21.4.4 and run a test, and now everything works fine. Are there any know problems with the 21.10.3 version?
EDIT 2: After the downgrade I again upgraded to 21.10.3… and now it is working there as well. I am stumped, but everything is fine now.

But question still stands: are there any problems with the newest version?

Thank you.


I see this is a kind of bug, It would be great if you send the bug the team, For sending this to their alert, check below

Hope this may help you


Hi @ripers

It looks similar to this one:

Our team had a look at that previous one and was unable to find steps that would result in a faulty, underlying XAML code.

Before it started working again for you, have you maybe edited your file? Redoing the steps in the workflow file should normally fix this issue and would explain why it is working for you now.

Would you be able to still share a XAML file that is causing this issue (either here or privately via a PM to me @loginerror)?