Problem with adding dependencies in 2019.1 CE library projects

Hey guys, since the CE update to 2019.1, I’m having trouble adding dependecies to Library projects. I keep getting the below error. Anyone know how to fix this? Sometimes it just doesn’t do anything at all, and sometimes it looks like it’s working, but instead of the green checkmark, there’s an error: “Package installation failure”

Error: System.NullReferenceException: Object reference not set to an instance of an object.
at UiPath.Studio.Shell.Packaging.PackagesLicensesValidator.d__4.MoveNext()
— 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.Packaging.PackagesLicensesValidator.d__3.MoveNext()
— 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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at UiPath.Studio.Shell.Packaging.PackageOperationBase.d__24.MoveNext()
— 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.Packaging.PackageOperationBase.<>c__DisplayClass23_0.<b__0>d.MoveNext()
— 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.Packaging.PackageOperationBase.d__23.MoveNext()
— 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.Packaging.PackageOperationUpdate.d__3.MoveNext()
— 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.Packaging.PackageService.<>c__DisplayClass32_0.<b__0>d.MoveNext()
— 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.Utilities.WindowCommandsExtensions.d__3`1.MoveNext()
— 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.PackageExplorer.UI.ViewModels.PackageExplorerViewModel.d__140.MoveNext(), HResult -2147467261

1 Like

Hi @evangemert

What dependencies are you trying to add?

1 Like

@loginerror
Mostly UiPath packages. But it looks like it happens on anything. Right now I’ve tried UiPath.Web.Activities, UiPath.Credentials.Activities and UiPath.Word.Activities. I’ve found a weird workaround though when the package fails to install, but does show up in the dependencies in the project. After I rightclick and hit ‘Repair dependency’, it works. But that’s still a nasty workaround, especially if you have to do it on all dependencies you want to add.

1 Like

Hi @evangemert

This post gives the basic troubleshoot:

I hope it helps. It might be happening due to some corruption in the packages and after the 1. point it will start working correctly.

Please keep us updated :slight_smile:

2 Likes

Looks like this fixed the problem, thank you!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.