Error "Only releases with status draft may be created on draft app." when no releases are in draft

[beeradmoore]

I am moving my CI/CD to Azure DevOps, and part of that is moving builds to Azure Pipeline.

My test Android app builds fine but while attempting to distribute to the store I get the error,

Only releases with status draft may be created on draft app.

But the problem is there is only 1 track being used, the internal track, and there is not a build in draft.

This is part of my current azure-pipelines.yml

    - task: GooglePlayRelease@4
      inputs:
        serviceEndpoint: 'GooglePlayConnection'
        track: 'internal'
        applicationId: '$(expectedBundleName)'
        action: 'SingleBundle'
        bundleFile: '$(platformSpecificOutputDirectory)/$(expectedBundleName).aab'
        releaseName: $(Build.BuildID)
        isDraftRelease: false
        changeLogFile: 'defaultReleaseNotes.txt'

If I change isDraftRelease to true it will upload but keep it in a draft state.

If I try follow up by immediately making the draft a completed app with

    - task: GooglePlayStatusUpdate@2
      inputs:
        serviceEndpoint: 'GooglePlayConnection'
        track: 'internal'
        packageName: '$(expectedBundleName)'
        status: 'completed'

but then that will fail with the same error

EDIT: I tried pushing to alpha instead of internal and got the same error even after pushing an app there manually.

[bryandam]

Subscribed.

Have the same issue: unreleased app in early testing that we want to automate test releases. Got the same error, added isDraftRelease: true which creates the app, but leaves it in draft mode.

There's previous closed issues talking about this and that it's solved with the isDraftRelease property, but not how to actually release said draft from the pipeline.

[ksheytanov]

I am experiencing exactly the same issue. Please post any updates or if there is a workaround.