How to create draft submission without publishing

[juliansteenbakker]

I can successfully submit a new version of my msix via msstore publish abc.msix -v -id abc, however this results in the submission being submitted directly. I want to change the changelog first, so i added -nc to keep it a draft, but this results in the .msix not being uploaded. I saw a similar issue here #50 (comment), but there isn't an answer on what i should do to achieve this.

[ia-jordan]

Facing the same issue.
We would like to automatically create the draft but let our marketing team look at the release before submitting it. Our only solution at the moment is to upload it by hand.
Would be nice if this could get fixed.

[michaeljolley]

Agreed. I'd love to submit my packages and then be able to manually update the "what's new in this release" before submitting.

[jranson]

Alexandre Zollinger Chohfi (@azchohfi) are you able to help us out here? I'm in the same boat and this issue has gone unaddressed. We need a way to have our GH Workflow submit a draft release to Partner Center that includes the workflow's updated msixupload files, so we can then manually in the Partner Center UX review (in case we want to adjust the Whats New) and advance the draft to the Certification stage. RIght now msstore publish <params> -nc creates the draft but Partner Center shows the Packages as 'Unchanged'. But if I run a subsequent msstore get for the Store ID, the resulting JSON (which includes invalid newlines that makes it unparsable, btw) shows the new Packages in the ApplicationPackages array alongside the old package versions. If I remove the old package versions from the JSON (while fixing the api-created invalid newlines too) and submit the modified JSON with msstore update, the cli returns 💥 Error!. So we can find no way to get the draft submission to reflect the new binaries in the UX, without hand uploading them. This is suboptimal and defeats the entire purpose of having the GH Workflow do automated builds for the Microsoft Store.

[azchohfi]

James Ranson (@jranson) I haven't been working on this for a while now.
knangunu is this something your team can look into? This seems like a simple fix in the CLI to adjust to some new JSON content.