-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Package resolution error #17
Comments
Yeah, I haven't check the experience in the editor since it was launched, so UPM might require new/different fields from the package/JSON-request-result that it was not requiring before. |
The strange thing is that I got the same inquiry from multiple users this week (I had never gotten one before). Did you change anything recently? |
The only PR merged recently that is related to changing something in the package is #12 but it's not related to this |
Actually, the issue is on UnityNuGet side, a change of the underlying JSON serializer used by ASP.NET that I haven't noticed. Should be fixable soon. |
This should be fixed by commit 59e685d And thanks for the report! My apology for the trouble, that was my mistake of upgrading to a newer version of ASP.NET that broke implicitly a few things. |
I verified that the issue was resolved. Thanks! |
Thank you two for acting so fast on this! 🎉 |
Package Manager fails to import packages via the UnityNuGet registry with the following error message.
I tested with Unity 2019.4 and 2020.1 (reproduced on both of them).
You have to clear the local package cache to reproduce the issue.
The text was updated successfully, but these errors were encountered: