SDCM-1.2024.730.1 failed to upload hlkx to partner center

[SenaryNick]

Describe the bug

Uploading Submission Package BlobStorageHandler DownloadToString - Exception uploading blob. Error - Object reference not set to an instance of an object.

To Reproduce I don't have ManagedIdentity, so I completed the authconfig.json as follows:

[
  {
    "tenantId": "***",
    "clientId": "***",
    "managedIdentityClientId": "",
    "scope":  "",
    "key": "***",
    "url": "https://manage.devcenter.microsoft.com",
    "urlPrefix": "v2.0/my"
  }
]

Then I built the project and run the command: SDCM\sdcm.exe -upload packages\3.49.6.2_UWP2.46.6.0_DCH_Acer_20240910_2-.hlkx -productid 13864755251377077 -submissionid 1152921505698248523

An exception was thrown: SurfaceDevCenterManager v1.0.0.1

Upload Option Fetch Submission Info initialPackage Url: * Uploading Submission Package BlobStorageHandler DownloadToString - Exception uploading blob. Error** - Object reference not set to an instance of an object. Correlation Id: 46a6e56b-f821-44bb-bd2e-0b307aaf3b58 Return: 0 (SUCCESS)

Expected behavior The hlkx file should have been uploaded successfully without any exception thrown.

Desktop (please complete the following information)

• OS: Win10 22H2 build 19045

Additional context

[idansella10]

@Ben-Carpenter we are facing the same issue. Since yesterday we cannot get our drivers signed using the SDCM tool. We are getting authorisation error “failed to authenticate the request. Make sure the value of Authorisation header is formed correctly including the signature.” while trying to solve this, we compiled the latest version of SDCM and now we get the same error as mentioned in this bug. Please advise

[idansella]

@Ben-Carpenter kindly find the following output log:

Executing upload step
sdcm.exe -upload C:\UE.cab -productid xxx -submissionid xxx
SurfaceDevCenterManager v1.0.0.1
> Upload Option
> Fetch Submission Info
> initialPackage Url: https://ingestionpackagesprod1.blob.core.windows.net/ingestion/xxx..xxx
> Uploading Submission Package
BlobStorageHandler DownloadToString - Exception uploading blob. Error - Object reference not set to an instance of an object.
Correlation Id: xxx
Return: 0 (SUCCESS)
Executing commit step
sdcm.exe -commit -productid xxx -submissionid xxx
SurfaceDevCenterManager v1.0.0.1
> Commit Option
> Sending Commit
ERROR (DevCenterErrorDetails)
Code:    entityNotFound
HttpCode:404
Message: Not found
Correlation Id: xxx
Return: -16 (COMMIT_API_FAILED)
Commit step failed``

[Ben-Carpenter]

We are looking into this issue.

As a reminder, please follow best security practices to not make credentials or sensitive information available online. Please remove any sensitive information from your comments, and we strongly advise to change your credentials ASAP since they are now publicly available on GitHub.

[tedops]

There seems to be an issue with the partner center as of a couple of days ago. Our submissions are coming back with 429 rate limit exceeded even though it's been 12+ hours since our last submission. Related?

[billziss-gh]

@Ben-Carpenter please note that GitHub still shows edited sensitive information. Perhaps this thread should be deleted and a new one started with all participants subscribed?

[Ben-Carpenter]

Please grab release 1.2024.911.1 and report any issues.

[Ben-Carpenter]

@Ben-Carpenter please note that GitHub still shows edited sensitive information. Perhaps this thread should be deleted and a new one started with all participants subscribed?

You can edit the comment, save, and then delete previous revision from history. Although it may be possible there are traces left in GitHub I would highly recommend rotating any credentials.

• https://stackoverflow.com/questions/69755177/how-to-remove-sensitive-information-from-issue-history-on-github
• https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository

[billziss-gh]

@Ben-Carpenter understood and thank you for the quick turnaround.

[Ben-Carpenter]

@Ben-Carpenter understood and thank you for the quick turnaround.

No problem. Thanks for reporting and participating in the community. Please let us know if you run into any other issues.

[SenaryNick]

Thanks. The previous key in the credential was removed.