none
Submission API returns 409 Conflict on our app RRS feed

  • Question

  • Hello,

    we are hitting the error 409 Conflict with our app when using StoreBroker (https://github.com/microsoft/StoreBroker) which uses the Submission API when calling  .\Extensions\ConvertFrom-ExistingSubmission.ps1 command. The error is as follows:

    The remote server returned an error: (409) Conflict.
    InvalidState : This application uses features that are not supported by the submission API. To perform this operation, use the Dev Center dashboard.

    I was able to find in the documentation (https://docs.microsoft.com/en-us/windows/uwp/monetize/create-and-manage-submissions-using-windows-store-services) that 409 is expected in these cases:

    This API cannot be used with apps or add-ons that use mandatory app updates and Store-managed consumable add-ons. If you use the Microsoft Store submission API with an app or add-on that uses one of these features, the API will return a 409 error code. In this case, you must use Partner Center to manage the submissions for the app or add-on.

    However, our app uses neither of these features. Is there another (undocumented) reason for the API to return 409?

    Any pointers to solution would be helpful!

    Monday, November 18, 2019 1:51 PM