´msstore publish´ hangs on Submission Status - CommitStarted

[meakbiyik]

Both on my workstation and CI, the msstore publish -i ".\release\build" command hangs on "Submission Status - CommitStarted". When I look at the partner center, I see that although the previous (manual) submission works without issues, the new submission by CLI appears buggy, see "Pricing and Availability" warning below. Waiting over 1 hour does not change the status. If it helps, there are no other errors, and it is an electron app.

[meakbiyik]

There does not seem to be anything out of ordinary in the logs when I run the command with ´-v´, only the following warnings repeat:

[azchohfi]

This is the normal execution of the publishing process. It will stay at Status=CommitStarted until it passes the first steps of certification, which might take a while. The CLI pools every 30 seconds, until it changes to something else, then it report it.

[meakbiyik]

Oh that I am aware, but should I expect it to take over 1 hour?

The behavior was consistent in my local and the Github Action, which is sadly not acceptable if we want to automate the publishing process.

To follow my steps: I have an electron app, I package it with npm exec electron-builder -- --win which builds the appx bundle, then I run msstore publish -i ".\release\build", and the code polls for one hour with the following output repeated and times out at the end.

[meakbiyik]

This is the normal execution of the publishing process. It will stay at Status=CommitStarted until it passes the first steps of certification, which might take a while. The CLI pools every 30 seconds, until it changes to something else, then it report it.

I also found one point in your comment interesting: does the CommitStarted status wait until the first steps of the certification process is concluded? Because the issue I report appear to happen before the certification starts, since the submission does not appear in a submitted for certification state on the user interface, see that the submit to the store button in the first figure I added still appears (yet disabled). Below is the UI for a properly submitted package:

My guess is that CLI configures the package metadata (most probably some field in the pricing and availability section) erroneously and therefore the package cannot be submitted to certification, and the app gets stuck in the commit started phase.

[meakbiyik]

I have a new symptom: without any changes to the pipeline or the cli, I started to get the following error (IDs are removed)

✅ Zip Bundle is configured and ready to be uploaded!
Uploading Bundle to Azure blob: 8%
Uploading Bundle to Azure blob: 72%
Uploading Bundle to Azure blob: 93%
✅ Successfully uploaded the application package.
Waiting for the submission commit processing to complete. This may take a couple
of minutes.
Submission Committed - Status=CommitStarted
Submission Status - CommitStarted

Submission Status - CommitStarted

Submission Status - CommitStarted

Submission Status - CommitStarted

Submission Status - CommitStarted

Submission Status - CommitFailed
                              ❗ Submission Errors                              
┌───────────────────────┬──────────────────────────────────────────────────────┐
│ Code                  │ Details                                              │
├───────────────────────┼──────────────────────────────────────────────────────┤
│ InvalidParameterValue │ Error. Request it is not IngestionWeb or             │
│                       │ IngestionApi. applicationId = xxx,            
│                       │ submissionId = xxx, The                  
│                       │ ClientIdentifier = IngestionAPIv1Worker              │
└───────────────────────┴──────────────────────────────────────────────────────┘

Submission has failed. Please check the Errors collection of the 
submissionResource response.

[azchohfi]

Are you still facing this issue?

[meakbiyik]

Yup, so I needed to disable auto-publish in the pipeline. Did you push a fix for it? I can test in the next release.

[azchohfi]

This seems to have been an intermittent issue with the service. I would try again, since we published a number of new versions or the cli.