Unable to fetch Azure packages from UPM

Azure / azure-spatial-anchors-samples

Azure Spatial Anchors sample code

Other

293 stars 139 forks source link

Unable to fetch Azure packages from UPM #262

Closed ian-phoria closed 3 years ago

ian-phoria commented 3 years ago

Description

I am unable to fetch the Azure packages directly through the Unity Package Manager. Is the package server currently down?

Steps to reproduce the issue

Attempt to update or fetch one of the azure packages from the Unity Package Manager
OR attempt to run a Unity Cloud Build with azure packages in your manifest.json

Screenshots AzurePackageManager01 AzureAccessDenied

Additional context

Project has been working correctly with Azure Spatial Anchors for about a year now. Issue only presented itself this morning (Monday) after working correctly on Friday.

ian-phoria commented 3 years ago

I've also noticed that your recommendation for importing the Azure packages into Unity has changed recently.

I initially had the Azure packages downloaded manually and locally included in the project but changed that to meet the ASA SDK v2.5.0 release requirements.

Have the requirements changed again? Is there no longer a way to pull the ASA packages directly using a scoped registry in the manifest.json as indicated:

If so, what's the reason for the change? ..and what's the recommended way to keep Unity projects up-to-date with the latest ASA SDK version?

ian-phoria commented 3 years ago

My mistake. I've just noticed that in a previous issue you announced that you are deprecating the old way of pulling the packages and that issues may arise after May 1st. Fair enough.

I've reopened the issue to ask where I should be looking for breaking Azure changes like this in future. Did I miss a more obvious and clear announcement of this change? ..or am I supposed to trawl the issues page every day in the hope I catch something like this earlier?

willyeo commented 3 years ago

Code breaking changes are announced in a couple of different ways: pinned post in the "Issues" channel here and direct emails if your email address is up-to-date in the azure portal where you created the ASA account.

This particular issue was a change to project configuration and not a code breaking change, therefore it was deemed sufficient to just have a pinned post in the channel which you mention. You can be made aware of this type of issue by "watching" (signing up for notifications) the this repo.

ian-phoria commented 3 years ago

Ah yep of course, I'll start watching the repo. Thank you for the quick response.

StephenHodgson commented 3 years ago

Yeah moving away from a scoped registry was a bad decision imho. I'm pretty sure that it breaks the TOS for package providers