OK looks like Unity team is aware of the issue, but still we would like to setup our DLL so it won’t run into similar issue in future. Is it possible?
Similar issues but completely different causes: Unity core changes.
[ 2021.2.0b6 and System.Memory/ReadOnlySpan under .NET 4.8 ]( 2021.2.0b6 and System.Memory/ReadOnlySpan under .NET 4.8 page-2)
To be fair, in my case disable “Validate References” works, but I imagine that’s because we got lucky as CompilerServices.Unsafe v4 and v5 are largely similar, and I am using a small fraction of the overall library.