UploadXvcPackage throws HttpRequestException

[VeliKokkonen]

UploadXvcPackage operation has started throwing the following exception.

fail: PackageUploader.ClientApi.Client.Ingestion.IngestionHttpClient[0] Exception: System.Net.Http.HttpRequestException: Response status code does not indicate success: 301 (Moved Permanently).    at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()    at PackageUploader.ClientApi.Client.Ingestion.Client.HttpRestClient.GetAsync[T](String subUrl, CancellationToken ct) in D:\PartnerCenter\GameStoreBroker\src\PackageUploader.ClientApi\Client\Ingestion\Client\HttpRestClient.cs:line 53

fail: PackageUploader.Application.Operations.UploadXvcPackageOperation[0] Response status code does not indicate success: 301 (Moved Permanently).

Upload operation has worked correctly in our deployment pipe month ago with the same setup. Tested with v1.7.5.

[nickfourtimes]

Noting that I have the same issue: it looks like the package was successfully uploaded on Partner Center, but then this response code seems like a false-negative, prompting our CI/CD system to abort distribution.

[Jakenv]

In our case we thought this error happened because we were trying to upload the same package twice, but recently even after removing package from the branch we still get the same error.

The biggest offender of this issues is that it indicates Error, returns code 3 and exits the program as failed. When checked on the Partner Center we can see that the app was uploaded but only msixvc file, the others(ekb, .zip and xml) were not uploaded presumably because upload failed on Processing

It would be nice if the program would return at least more meaningful error than generic 301
Best case if it would just ignore the error and just continue with the upload

[justlordington]

Running into this issue as well from latest source. Seems to upload all the files successfully then reports the 301.

[thunderfultim]

We are also seeing this for MsStore packages (but not other package types) on 1.7.6.