[BUG 2.1.0] VCC fails to import a VPM asset (vauge error output)

[techanon]

Describe the bug
VCC is failing to import an asset. It spits out some un-specific error.

To Reproduce
Steps to reproduce the behavior:

1. https://vpm.techanon.dev and add to VCC (requires pre-release)
2. Attempt to add to a project
3. Check the logs for errors

Expected behavior
The package should succeed on importing.

Screenshots
The logs spits out twice One or more errors occurred. (Object reference not set to an instance of an object.)

[techanon]

Originally thought it was tied to legacy folders, but I removed that entire part from the json and still failing in the same way. Continuing to test things.

[orels1]

Gitlab doesn't supply a Content-Disposition: attachment header, which is what the VCC is checking for, which is probably unnecessary.

This currently causes your package to fail to download

[techanon]

Appears so yes. In the mean time I found an alternative gitlab API to upload to which does appear to provide the requisite headers as I am able to import properly now. Thank you for the heads up on that.

[esperecyan]

Because it does not return content-disposition, GitHub Pages cannot also be used.

[momo-the-monster]

This should be fixed in https://github.com/vrchat-community/vrc-package-manager/pull/366

[momo-the-monster]

Should be fixed in VCC 2.1.2!