All app-specific queries return 409 | Conflict

[InflexCZE]

We'd like to start using StoreBroker for automated submission uploads.
After successfull authentication we can query basic information about our apps/titles without issues but any app-specific query fails for us with error 409 | Conflict (Examples attached below).

idds@xbox.com confimed for us that our apps are clear from all setting that could block the Submission API (namely “mandatory app updates” and “consumable add-ons”).

Is there any way to get more info on what could be wrong, which app/Partner Center setting is causing the 409 conflict?

Error logs

> .\Extensions\ConvertFrom-ExistingSubmission.ps1 -AppId 9NLV3X229LG1 -Release 0420 -PdpFileName PDP.xml -OutPath C:\Users\martin.pavlicek\Desktop\StoreBroker
  DONE (FAILED) - Operation took 7 second(s) [Getting data for AppId: 9NLV3X229LG1]
  Write-Log : 2020-05-25 13:11:10 : martin.pavlicek : 409 | Conflict
  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.
  MS-CorrelationId: a1be2571-41d4-43f2-b994-6c3e863345f1
  At C:\Users\martin.pavlicek\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\StoreIngestionApi.psm1:2125 char:17
  +                 Write-Log -Message $newLineOutput -Level Error
  +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

  409 | Conflict
  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.
  MS-CorrelationId: a1be2571-41d4-43f2-b994-6c3e863345f1
  At C:\Users\martin.pavlicek\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\StoreIngestionApi.psm1:2127 char:17
  +                 throw $newLineOutput
  +                 ~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : OperationStopped: (409 | Conflict...94-6c3e863345f1:String) [], RuntimeException
      + FullyQualifiedErrorId : 409 | Conflict
  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.
  MS-CorrelationId: a1be2571-41d4-43f2-b994-6c3e863345f1

> New-StoreBrokerConfigFile -Path (Join-Path -Path ([System.Environment]::GetFolderPath('Desktop')) -ChildPath 'SBConfig.json') -AppId 9NLV3X229LG1
  DONE (FAILED) - Operation took 18 second(s) [Getting data for AppId: 9NLV3X229LG1]
  Write-Log : 2020-05-25 13:11:38 : martin.pavlicek : 409 | Conflict
  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.
  MS-CorrelationId: c99f02f6-a6dc-42f9-b107-0b9485d74cbe
  At C:\Users\martin.pavlicek\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\StoreIngestionApi.psm1:2125 char:17
  +                 Write-Log -Message $newLineOutput -Level Error
  +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

  Write-Log : 2020-05-25 13:11:38 : martin.pavlicek : Encountered problems getting current application submission values:
  409 | Conflict
  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.
  MS-CorrelationId: c99f02f6-a6dc-42f9-b107-0b9485d74cbe
  At C:\Users\martin.pavlicek\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\StoreIngestionApi.psm1:2127 char:17
  +                 throw $newLineOutput
  +                 ~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : OperationStopped: (409 | Conflict...07-0b9485d74cbe:String) [], RuntimeException
      + FullyQualifiedErrorId : 409 | Conflict
  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.
  MS-CorrelationId: c99f02f6-a6dc-42f9-b107-0b9485d74cbe

  At C:\Users\martin.pavlicek\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\PackageTool.ps1:371 char:9
  +         Write-Log -Message "Encountered problems getting current appl ...
  +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

  409 | Conflict
  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.
  MS-CorrelationId: c99f02f6-a6dc-42f9-b107-0b9485d74cbe
  At C:\Users\martin.pavlicek\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\StoreIngestionApi.psm1:2127 char:17
  +                 throw $newLineOutput
  +                 ~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : OperationStopped: (409 | Conflict...07-0b9485d74cbe:String) [], RuntimeException
      + FullyQualifiedErrorId : 409 | Conflict
  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.
  MS-CorrelationId: c99f02f6-a6dc-42f9-b107-0b9485d74cbe

[HowardWolosky]

Do you use Sandboxes at all? That's another thing that's incompatible with v1 of the API (supported in v2).

[InflexCZE]

Yes, we have special sandbox for development.
Should I switch to V2 branch, is it "production ready"?

[HowardWolosky]

The v2 API isn't publicly available yet, and so only developers whose accounts have been whitelisted are able to access it. Let me reach out to the Windows Store team to see if it would be possible to get your account whitelisted. No promises.

[InflexCZE]

Did the Windows Store team get back to you with some positive news?
Can we apply to the beta program via some official way if that didn't work out?

[HowardWolosky]

They haven't responded yet. I sent another message. There is no other way at present time to get access to v2.

[HowardWolosky]

Hi @InflexCZE,

The Windows Submission API team is not onboarding additional users to the v2 API at this time.

Sorry that I don't have better news for you :(