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

Unity keeps Resolving packages when switching between clone and original. #23

Closed
tarsss opened this issue Jan 10, 2021 · 6 comments
Closed

Comments

@tarsss
Copy link

tarsss commented Jan 10, 2021

I have a single clone of my project to test Mirror multiplayer. But when I switch between original and clone project editors, "Resolving packages" window appears, and takes few seconds to complete, which is kinda annoing. I already tried to clone original project again, but still, the issue is there. It seems like packages between original and clone are conflicting in some way (?). Is there any way to fix this? Thanks.

@314pies
Copy link
Contributor

314pies commented Jan 10, 2021

Hi tarsss,
Thanks for reaching out.
Would you mind to show us how to reproduce it so we can take a deeper look?

@tarsss
Copy link
Author

tarsss commented Jan 10, 2021

Thanks for your quick reply!
The steps for replicating the issue:

  1. Create a new 2D Unity project with Unity Hub
  2. Clone it, and open the cloned project via Clone Manager
  3. Switch between original and cloned editor windows several times

The Unity version is 2019.4.17f1. Also tried with 2019.4.9f1 though.
Here's link to the archive with original and cloned projects: https://drive.google.com/file/d/1IRObhri95PFqHiC1mj0ZIYrJ55LHHEZp/view?usp=sharing

@tarsss
Copy link
Author

tarsss commented Jan 11, 2021

I've replaced clone's Packages folder with the one from original project. Looks like the problem is solved now

@anisimovih
Copy link

You can also turn off Auto Refresh in the preference panel and save changes only when you actually change something.

@TheYellowArchitect
Copy link

TheYellowArchitect commented Feb 5, 2021

I've replaced clone's Packages folder with the one from original project. Looks like the problem is solved now

Huh. Thank you guys. I was at a loss on what was at fault
#29

Works now. I just deleted the symlink to Packages, and just copy-pasted the Packages. It just works.

@314pies
Copy link
Contributor

314pies commented Apr 28, 2021

This have been fixed in the latest released.
Please check it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants