Compile errors after upgrade to 3.0.1 due to not referenced projects

[Asse1]

Hey guys,

we upgrade the Unity Purchasing package from 2.x to 3.0.1 and after that we got lots of compile errors.

We use several asmdef files to manage our projects and the compile errors appear since the Purchasing packages aren’t referenced in out projects. So I needed to check in which Purchasing library the missing classes are included and referenced those Purchasing asmdef files.

This solved the missing classes one after the other but at some point Unity didn’t manage to really include all the Purchasing projects in to our projects, even so they’re referenced in our asmdef files.

Referenced asmdef files in Unity:

VS project referenced assemblies:

Of course this stil leads to compile errors.

I also tried moving the referenced asmdefs up and down but nothing works. We work with asmdef files a lot and never had problems with that.

Of course the old Purchasing 2.x files are already deleted and I followed all other migration tasks.

Any suggestions?

[JeffDUnity3D]

@Asse1 Please provide steps to reproduce using a new/minimum project. I would not know what errors you might be seeing. We have other users using asmdefs without issue.

[Asse1]

It seems like I also needed to include “UnityEngine.Purchasing.SecurityStub”, even so no classes of this assembly are used directly.

Everything is referenced as expected afterwards.

[Ghetaldus]

I just upgraded from v2 => v3 as well and had some issues with asmdef references.
Before upgrade I had to just use UnityEngine.Purchasing reference.
Now after update I have to use all following references to make it work.

Seems like there is some issues with references in v3.

[JeffDUnity3D]

@Ghetaldus

I just upgraded from v2 => v3 as well and had some issues with asmdef references.
Before upgrade I had to just use UnityEngine.Purchasing reference.
Now after update I have to use all following references to make it work.

Seems like there is some issues with references in v3.

That is expected.