Failed to publish. error: InvalidPricingAvailabilitySettings

I am trying to publish an update for my app using the msstore CLI, and I am running into a CommitFailed error with the code InvalidParameterValue. It seems to be related to the app's pricing and availability settings.

🐛 Bug Report

I'm using the msstore CLI tool to publish a WinUI 3 app update. Here is the command I'm running and the resulting error:

Command:

msstore publish -i "X:\Projects\winui3_app\" -v -id <AppID>

Error Output:

Submission Status - CommitFailed
                              ❗ Submission Errors                              
┌───────────────────────┬──────────────────────────────────────────────────────┐
│ Code                  │ Details                                              │
├───────────────────────┼──────────────────────────────────────────────────────┤
│ InvalidParameterValue │ Validation error: InvalidPricingAvailabilitySettings │
│                       │ -                                                    │
└───────────────────────┴──────────────────────────────────────────────────────┘
11:34:51 info: MSStore.CLI.ProjectConfigurators.WinUIProjectConfigurator[0] 
SalesUnsupportedWarning - The sales resource is no longer supported. To view or edit the sales data for this submission, use the Dev Center dashboard.
Submission has failed. Please check the Errors collection of the submissionResource response.

When checking the Dev Center dashboard for the app, I noticed an error on the Pricing and availability page:

You can’t customize the schedule for a product that is hidden in the Microsoft Store.

This error message suggests that the publishing tool might be trying to set a schedule or pricing details that are not allowed for an app that is currently hidden in the store. This is a likely cause for the InvalidPricingAvailabilitySettings validation error.

❓ Question

Is the msstore publish tool attempting to modify the pricing or availability schedule by default, even when no related parameters are specified? If so, this seems like a bug, as it should respect the current state of a hidden app and not attempt to perform an invalid action.

I would appreciate any guidance on whether this is an issue with the tool itself or if I am missing a specific configuration or parameter that would prevent this behavior.

Thanks for your help!

Begin with the msstore publish command and the MSStore.CLI.ProjectConfigurators.WinUIProjectConfigurator path named in the log; compare the submission's pricing and availability data with the hidden-app restriction shown in Dev Center. Reproduce using the provided command and confirm done when the behavior is corrected or the CLI reports a clear, actionable configuration error.