search

microsoft / StoreBroker

A PowerShell module that leverages the Windows Store Submission API to allow easy automation of application submissions to the Windows Store. The master branch is stable and the v2 branch is under active development.
Other
97 stars 40 forks source link

Failed to commit after using Set-ApplicationSubmission #249

Closed CheeryLee closed 5 months ago

CheeryLee commented 5 months ago

Hi!

I'm trying to make a new submission via StoreBroker. Found the problem that any changes that provided with Set-ApplicationSubmission causes commit to fail in the end. It doesn't matter which property would be changed. It's enough to just run the command with the source submission object.

What I'm getting with Start-SubmissionMonitor:

Submission Status : CommitFailed

Status Details [Errors]                :
     code                  details
     ----                  -------
InvalidParameterValue Error. Request it is not IngestionWeb or IngestionApi. applicationId = <my app id>, submissionId = 1152921505697533853, The ClientIdentifier = IngestionAPIv1Worker

Steps to reproduce:

  1. create new submission: $sub = New-ApplicationSubmission -AppId <app_id>
  2. run this WITHOUT changing anything in $sub object: Set-ApplicationSubmission -AppId <app_id> -UpdatedSubmission $sub
  3. make a commit: Complete-ApplicationSubmission -AppId <app_id> -SubmissionId ($sub.id)
  4. check the submission status using Start-SubmissionMonitor

I don't really understand what this error means. The code InvalidParameterValue usually tells us that something in the submission body is wrong, but details is completely useless unfortunately.

MrCapitalQ commented 5 months ago

I am also getting this error starting on March 15th. I can see the same error message when using the Get-ApplicationSubmission call to see why my submissions aren't going through. This happened once before that but went away by itself after a couple weeks. Both times, my usage of the StoreBroker did not change when this error started to occur so I'm thinking something changed server side? Not sure how to proceed here.

JohanLorenzo commented 5 months ago

Same here, we started seeing it on March 19th.

HowardWolosky commented 5 months ago

Thanks for the report everyone. I was on vacation so my response was delayed. I've reached out to the Store API team to let them know about the issue. I'll report back here when I hear back from them.

HowardWolosky commented 5 months ago

The API team reports that they have deployed the fix, so things should be working again. Closing this issue now.

JohanLorenzo commented 5 months ago

Thanks Howard! I confirm this works on my end 👍

mkaply commented 5 months ago

What was the issue?

HowardWolosky commented 5 months ago

What was the issue?

Unfortunately, I don't have that info. All I know is that they deployed an update to the API service backend to resolve it.