I’ve encountered another problem following upgrade Studio 22.10.3, update of activity packages and migration of project from Windows Legacy to Windows.
On running the project under debug, starting with Main, even before a single workflow activity has started (i.e. when use Step Into or with breakpoint on the very first breakpoint possible, the TryCatch in the Initialization state of the framework), the following exception is thrown:
System.ArgumentException: An item with the same key has already been added. Key: VisualBasicValue
1_1 at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
1 source, Func2 keySelector, Func
2 elementSelector, IEqualityComparer1 comparer)
at UiPath.Executor.Tracking.ActivityIdsResolver.Register(WorkflowInfo workflowInfo)
at UiPath.Executor.Tracking.DebugTrackingParticipant.RegisterWorkflow(WorkflowInfo workflowInfo)
at UiPath.Executor.DebuggerPlugin.UiPath.Executor.IDebuggerPlugin.RegisterWorkflowTracking(WorkflowInfo workflowInfo)
at UiPath.Executor.Tracking.WorkflowTracking.RegisterWorkflowTracking(WorkflowInfo workflowInfo)
at UiPath.Executor.WorkflowRuntime.RegisterWorkflow(WorkflowInfo workflowInfo)
There is no mention of any specific activity in the exception, no activity is navigated to and highlighted automatically, as is normal with run-time errors.
I am not aware of any change to .Net that prevents an assign statement that would update a value of an existing key, that if the key doesn’t exists would instead create the new key.
I’ve no explanation of this behavior which is entirely unexpected and urgently need a solution.
UiPath support, please advise if I need to formally raise a case to you via vendor.