Input Dialog:Object reference not set to an instance of an object

Help Activities
1

The Input Dialog activity throws the error “Object reference not set to an instance of an object” when I run the file. I already tried reinstalling the program and deleting/reinstalling the packages. This only happens when I leave the Input Type set to Text Box.

Here is the error shown in the debugger:

RemoteException wrapping System.NullReferenceException: Object reference not set to an instance of an object.
at UiPath.Core.Activities.InputDialog.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance,
ActivityExecutor executor,
BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor,
BookmarkManager bookmarkManager,
Location resultLocation)

2

I have seen a ton of questions regarding this, and can confirm the same behavior on an Input Dialog activity that was working. If you select “Multiple Choice” as the Input Type, and add “” to ‘Options String’ property, it goes through fine as a text box. I think there is a bug in the latest version with ‘Text Box’ Input Type.

3

Hi,

It seems there is problem with InputDialog activity in UiPath.System.Activities package 26.2.0 or higher .
Another solution is to downgrade it to version 25.12.2 or lower. However, please note that downgrading may cause existing activity to crash. In this case, it’s necessary to replace it OR create workflow using the version from the beginning.

Regards,

4

Hi,

Upload your activity version in : 25.12.2, that’s resolve your pb.

5

Hi,

I encounter the same problem, what I did were
for Input Type as Text Box, you can add empty array string {“”} to “Option” Property.

image 1
image 1451×280 15.5 KB

Hope this helps.

6

Hello @aeb2b0124551be751c1f43e29,

There is an issue with the System activities version. Please upgrade UiPath.System.Activities to v26.2.3

Thanks,
Karthik

7

As mentioned by @chinthakayala_karthik, this is indeed fixed in the latest version of System 26.2.3: