Connector.Salesforce.Activities causing "Document is invalid" errors

We use version 1.1.0 of Connector.Salesforce.Activities to interact with Salesforce for some of our bots.
Sometime yesterday morning (as far as I can tell) the activity stopped working. If I install the activity I am unable to open the workflow with the reason given as “Document is invalid”. The document will load if the activity is uninstalled but then the robot can’t interact with Salesforce, which it needs to do.

Full stack trace:

The item '...Main.xaml' could not be opened: Document is invalid.

Cannot open item: UiPath.Studio.Contracts.RecoverableException: The item '...Main.xaml' could not be opened: Document is invalid. ---> System.IO.InvalidDataException: Document is invalid
   at UiPath.Studio.Plugin.Workflow.WorkflowHandling.DesignerWrapper.InitRootActivity(String filename) in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\WorkflowHandling\DesignerWrapperInit.cs:line 247
   at UiPath.Studio.Plugin.Workflow.WorkflowHandling.DesignerWrapper.Load(String fileName) in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\WorkflowHandling\DesignerWrapperInit.cs:line 72
   at UiPath.Studio.Plugin.Workflow.Services.DesignerFileService.<>c__DisplayClass10_0.<Load>b__0() in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\Services\DesignerFileService.cs:line 107
   at UiPath.Studio.Shared.MVVM.Services.DispatcherExtensions.Invoke(Dispatcher dispatcher, Action action, Boolean onlyBeginInvokeWhenNoAccess) in D:\a\1\s\Studio\UiPath.Studio.Shared\MVVM\Services\Extensions\DispatcherExtensions.cs:line 121
   at UiPath.Studio.Shared.MVVM.Services.DispatcherService.Invoke(Action action, Boolean onlyInvokeWhenNoAccess) in D:\a\1\s\Studio\UiPath.Studio.Shared\MVVM\Services\DispatcherService.cs:line 165
   at UiPath.Studio.Plugin.Workflow.Services.DesignerFileService.Load(String fileName) in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\Services\DesignerFileService.cs:line 88
   at UiPath.Studio.Plugin.Workflow.Services.Interfaces.IDesignerFileService.Load(String fileName)
   at UiPath.Studio.Plugin.Workflow.Services.DesignerFileServiceProxy.Load(String fileName) in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\Services\Proxies\DesignerFileServiceProxy.cs:line 20
   at UiPath.Studio.Plugin.Workflow.WorkflowDocument..ctor(String path, IDesignerFileService designerFileService, IExtendedFileSystem fileSystem, IDesignerViewService designerViewService) in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\Document\WorkflowDocument.cs:line 53
   at UiPath.Studio.Plugin.Workflow.WorkflowDocumentFactory.OpenAsync(String path) in D:\a\1\s\Studio\UiPath.Studio.Plugin.Workflow\Document\WorkflowDocumentFactory.cs:line 253
   at UiPath.Studio.Shell.Services.PersistableServiceBase`3.<OnOpenAsync>d__15.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shell\Services\PersistableServiceBase.cs:line 178
   --- End of inner exception stack trace ---
   at UiPath.Studio.Shell.Services.PersistableServiceBase`3.<OnOpenAsync>d__15.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shell\Services\PersistableServiceBase.cs:line 188
--- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at UiPath.Studio.Shell.Services.DocumentService.<OnOpenAsync>d__45.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shell\Services\DocumentService.cs:line 353
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at UiPath.Studio.Shell.Services.PersistableServiceBase`3.<OpenAsync>d__8.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shell\Services\PersistableServiceBase.cs:line 0
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at UiPath.Studio.Shell.ViewModels.Project.FileProjectItemViewModel.<OpenExecute>d__11.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shell\ViewModels\Project\FileProjectItemViewModel.cs:line 73
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at UiPath.Studio.Shell.ViewModels.Project.FileSystemProjectItemViewModelBase.<<-ctor>b__9_0>d.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shell\ViewModels\Project\FileSystemProjectItemViewModelBase.cs:line 59
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at UiPath.Studio.Shared.MVVM.Commands.TaskCommand`3.<Execute>d__35.MoveNext() in D:\a\1\s\Studio\UiPath.Studio.Shared\MVVM\Commands\TaskCommand.cs:line 282
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler), HResult -2146233088

Hi @DanielMitchell

Is there anything else that changed when it stopped working?

Does it happen for the newly created, blank project as well?

As far as I was able to tell nothing else changed, but that doesn’t make much sense.

I was able to get the process working by doing two things:

  1. The specific machine that broke was running 2018.2.6 so I updated to 2018.4.2
  2. I deleted the Salesforce activities that were breaking the robot and then just replaced them from the activities panel. The fresh ones caused no errors.

Another interesting issue is that on another robot machine (running 2018.2.6) I was unable to uninstall the Connector.Salesforce.Activities package from Studio.