If we migrate Legacy Projects, VCC will install SDK 3.5.0(or 3.5.0-beta.1) and Package Resolver Tool 0.1.27, even though the project unity version is 2019.4.31f1.
This leads destroy the project.
To Reproduce
Open VCC
Do "Add Existing Project" and add Legacy project
Click "Upgrade SDK"
Migrate non-VCC to VCC
Click "Manage Project"
SDK is 3.5.0(or 3.5.0-beta.1) and Package Resolver Tool is 0.1.27
Expected behavior
Install SDK 3.4.2 and Package Resolver Tool 0.1.26. (Latest version for Unity 2019.4.31f1)
Screenshots
No response
Related Product
VCC (VRChat Creator Companion)
Product Version
2.2.3
OS
Windows 10
Additional context
I think VCC is not checking the unity field when migrating legacy projects.
I'm not tested this on VPMCLI, but I suspect it also have the same problem.
Describe the bug
If we migrate Legacy Projects, VCC will install SDK 3.5.0(or 3.5.0-beta.1) and Package Resolver Tool 0.1.27, even though the project unity version is 2019.4.31f1. This leads destroy the project.
To Reproduce
Expected behavior
Install SDK 3.4.2 and Package Resolver Tool 0.1.26. (Latest version for Unity 2019.4.31f1)
Screenshots
No response
Related Product
VCC (VRChat Creator Companion)
Product Version
2.2.3
OS
Windows 10
Additional context
I think VCC is not checking the unity field when migrating legacy projects. I'm not tested this on VPMCLI, but I suspect it also have the same problem.