MSStore CLI emits informational/success logs to stderr resulting in false-positive Azure DevOps pipeline failures

[rewyekha]

Issue Summary

MSStore CLI successfully publishes an MSIX package to Microsoft Store; however, informational and success messages are emitted to stderr instead of stdout.

In Azure DevOps Release Pipelines, stderr output is interpreted as task errors and is rendered as ##[error], causing false-positive deployment failures despite successful Store submission processing.

---

Issue Details

The publish workflow completes successfully:

1. Application lookup succeeds.
2. Submission creation succeeds.
3. Package upload succeeds.
4. Submission commit succeeds.
5. Submission status progresses normally.
6. Package is visible in Partner Center.

Observed API response codes:

GET  -> 200
POST -> 201
PUT  -> 200
POST Commit -> 202

Final CLI output indicates successful completion:

✅ Ok! Found the app!
✅ Submission created.
✅ Successfully uploaded the application package.
Submission Status - PreProcessing
✅ Submission retrieved
Submission commit success!

---

Problem

The same successful execution generates stderr entries such as:

##[error] ✅ Ok! Found the app!
##[error] ✅ Submission created.
##[error] ✅ Successfully uploaded the application package.
##[error] Submission commit success!

Azure DevOps interprets these stderr messages as task errors.

As a result:

• Deployment is successfully created in Partner Center.
• Submission processing continues normally.
• Package becomes available in Store workflow.
• Release stage may be flagged as failed or partially failed.
• Monitoring and deployment reporting become unreliable.

---

Additional Observation

The following warning is emitted through stderr:

SalesUnsupportedWarning - The sales resource is no longer supported.

While this warning is informational, it is surfaced as an Azure DevOps error due to stderr handling.

---

Any solution please