Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] migrate Legacy Project will install incompatible version of packages #410

Closed
Sayamame-beans opened this issue Dec 20, 2023 · 1 comment
Closed

[BUG] migrate Legacy Project will install incompatible version of packages #410

Sayamame-beans opened this issue Dec 20, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Sayamame-beans
Copy link

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

  1. Open VCC
  2. Do "Add Existing Project" and add Legacy project
  3. Click "Upgrade SDK"
  4. Migrate non-VCC to VCC
  5. Click "Manage Project"
  6. 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.
@Sayamame-beans Sayamame-beans added the bug Something isn't working label Dec 20, 2023
@momo-the-monster
Copy link
Contributor

Should be fixed in release 2.2.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@momo-the-monster @Sayamame-beans