UnityNuGet: Can't use NuGet packages with 4 (or more) dot version number

I tried out UnityNuGet, by running it locally, and adding dependencies for OPCFoundation.NetStandard.Opc.Ua.Client. This package has versions with 4 parts. For example the latest version is: 1.4.367.41. When trying to import it with the package manager, I get an error:

[Package Manager Window] Cannot perform upm operation: Unable to add package [org.nuget.opcfoundation.netstandard.opc.ua.client@1.4.367-41]:
  Package org.nuget.opcfoundation.netstandard.opc.ua.client@1.4.367-41 has invalid dependencies or related test packages:
    org.nuget.opcfoundation.netstandard.opc.ua.configuration (dependency): Version '1.4.367.41' is invalid. Expected a 'SemVer' compatible value.
    org.nuget.opcfoundation.netstandard.opc.ua.core (dependency): Version '1.4.367.41' is invalid. Expected a 'SemVer' compatible value. [NotFound].
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()

Edit: Also i could not see any warning or error coming from the server.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15 (12 by maintainers)

Most upvoted comments

@KuraiAndras that Tarball problem I think that it’s a discrepancy on unityNuget registry vs your local machine cache. If you clean your local cache I think that it should be fixed.

bdovaz on Oct 5, 2021

@KuraiAndras PR added:

https://github.com/OPCFoundation/UA-.NETStandard/pull/1551

bdovaz on Oct 17, 2021

@KuraiAndras that Tarball problem I think that it’s a discrepancy on unityNuget registry vs your local machine cache. If you clean your local cache I think that it should be fixed.

Yes, I forgot to mention, the old cache will cause many conflicts and needs to be deleted manually

xoofx on Oct 5, 2021

@KuraiAndras I have seen before the problem you are facing.

It’s because some packages have dependencies on packages that are already on .NET Standard 2.0+ runtime so there shouldn’t be there defined as dependencies.

For example, the following dependencies have no updates since 2016:

https://www.nuget.org/packages/System.Data.Common/ https://www.nuget.org/packages/System.Net.NameResolution/

In some cases I have created PR’s to fix this problem that it’s only “a problem” with Unity + UnityNuget.

bdovaz on Oct 5, 2021

Oh, it’s actually a bug in the dependencies, let me see If I can fix it

xoofx on Oct 5, 2021