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

Package resolution error #17

Closed
keijiro opened this issue Nov 5, 2020 · 7 comments
Closed

Package resolution error #17

keijiro opened this issue Nov 5, 2020 · 7 comments
Labels
bug Something isn't working

Comments

@keijiro
Copy link
Contributor

keijiro commented Nov 5, 2020

Package Manager fails to import packages via the UnityNuGet registry with the following error message.

Screenshot from 2020-11-05 21-36-46

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.

@xoofx xoofx added the bug Something isn't working label Nov 5, 2020
@xoofx
Copy link
Owner

xoofx commented Nov 5, 2020

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.

@keijiro
Copy link
Contributor Author

keijiro commented Nov 6, 2020

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?

@xoofx
Copy link
Owner

xoofx commented Nov 6, 2020

The only PR merged recently that is related to changing something in the package is #12 but it's not related to this tarball field missing...
I would think that something has changed in UPM. I have identified for example that the field tarball is no longer under the field distribution but dist, so could it could just that. I will try to see if that fixes it.

@xoofx
Copy link
Owner

xoofx commented Nov 6, 2020

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.

@xoofx
Copy link
Owner

xoofx commented Nov 6, 2020

This should be fixed by commit 59e685d
I just tested with UPM on a 2020.1.12f1 version and the packages are back in the UI.

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.

@xoofx xoofx closed this as completed Nov 6, 2020
@keijiro
Copy link
Contributor Author

keijiro commented Nov 6, 2020

I verified that the issue was resolved. Thanks!

@hybridherbst
Copy link
Contributor

Thank you two for acting so fast on this! 🎉

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

No branches or pull requests

3 participants