microsoft / msstore-cli

Microsoft Store CLI
MIT License
72 stars 7 forks source link

Improve error messages - "Language codes: en-US not supported" #31

Closed Juliotati closed 1 month ago

Juliotati commented 3 months ago

After repeatedly this getting this error, I'm not sure what it means or what is even causing the error. If possible please provide richer error messages or tips on what could have caused the error.

Is this an issue on my project or from msstore-cli itself?

Screenshot 2024-03-31 at 10 43 55

Error json response

{
  "code": "InvalidParameterValue",
  "data": [],
  "details": [],
  "message": "Language codes: en-US not supported",
  "source": "Ingestion Api",
  "target": "appListings"
}
azchohfi commented 1 month ago

We can't do much to improve the error messages, as these are coming from the API itself. I believe this might be the listing language is not matching what you have in your msix. Which command was issues and what is the type of project trying to be published?

Juliotati commented 1 month ago

We can't do much to improve the error messages, as these are coming from the API itself. I believe this might be the listing language is not matching what you have in your msix. Which command was issues and what is the type of project trying to be published?

Thanks for the update and yes I was suspecting that the errors are something that would have to improved elsewhere.

Type of project: Flutter Desktop App

Not sure if this is a normal error that appears on first releases are not, and if my memory isn't failing me, I believe I did try matching the language code, but still got the error.

The error came from my workflow step executed by:

msstore publish -i build/windows/x64/runner/Release/ --appId $PRODUCT_ID -v

But it seem that the package does get sent over to partner center for manual publishing after running msstore reconfigure even before or without running msstore publish.

At the moment I'll wait and see what happens after successfully manually publishing the app on the store. (no rush)

azchohfi commented 1 month ago

This seems to be a regression in the API. 'en-US' should now be 'en-us'. We are pushing a small fix for this.

azchohfi commented 1 month ago

Should be fixed on v0.1.33.