When userFraction is not set, PlayStore console sets the rollout percentage to 1%

[rafaelvcaetano]

Describe the bug When the userFraction parameter is not set, the release overview in PlayStore shows a default rollout percentage of 1% instead of the expected 100% (see image below).

Workflow Step Configuration

- name: Create Play Store Release
  uses: r0adkll/[email protected]
  with:
    serviceAccountJsonPlainText: ${{ <<REDACTED>> }}
    packageName: <<REDACTED>>
    releaseName: ${{ steps.release_params.outputs.VERSION }}
    releaseFiles: <<REDACTED>>
    track: beta
    inAppUpdatePriority: 2
    status: draft
    whatsNewDirectory: <<REDACTED>>
    mappingFile: <<REDACTED>>
    debugSymbols: <<REDACTED>>

Step Debugging

• [ ] I have enabled Step Debug Logging

[boswelja]

That's an interesting one. In theory, that's impossible, since we default to a "complete" rollout, which cannot have a user fraction set (Google Play forces 100%, it's an error to even specify it).

Does this happen consistently? If so, please try enabling debug logging and share the output

[rafaelvcaetano]

Sorry for leaving this here for so long. So, it turns out that the userFraction parameter is ignored by Play Developer API if the release status is set to draft, which is what I had. It seems to default to 1%. If set to completed, everything works fine. It was just a misunderstanding from my part that I only got clarified once I read the API's documentation. Maybe it's a good idea to leave that clear in the README to remove any confusion from future users, but I'll leave that up to you 🙂

[boswelja]

Sounds like a good idea to me, I didn't know about that behaviour either 😆