Ability to release to more than one track in single build

[richard457]

track: [beta,production] is this possible?

[amitav13]

I'm looking for this as well. This is my current non-working setup:

- name: Upload to Beta track on Play Store
        if: ${{ contains(env.RELEASE_VERSION, 'beta') }}
        uses: r0adkll/upload-google-play@v1
        with:
          serviceAccountJsonPlainText: ${{ secrets.SERVICE_ACCOUNT_JSON }}
          packageName: my.app
          releaseFiles: app/build/outputs/bundle/prodRelease/app-prod-release.aab
          track: beta
          whatsNewDirectory: releaseNotes
          mappingFile: app/build/outputs/mapping/prodRelease/mapping.txt
      - name: Upload to Production track on Play Store
        if: ${{ contains(env.RELEASE_VERSION, 'prod') }}
        uses: r0adkll/upload-google-play@v1
        with:
          serviceAccountJsonPlainText: ${{ secrets.SERVICE_ACCOUNT_JSON }}
          packageName: my.app
          releaseFiles: app/build/outputs/bundle/prodRelease/app-prod-release.aab
          track: production
          whatsNewDirectory: releaseNotes
          mappingFile: app/build/outputs/mapping/prodRelease/mapping.txt

This gives me an error since if I try to do a prod release with the same aab since the versionCode is already taken. Rather than a new release, we need to "promote" the release from beta to prod.

[boswelja]

Copying from #97

As far as I'm aware, higher tracks supersede lower tracks. For your example, I'd expect publishing to beta would also update users running older builds on internal. An I missing something?

[amitav13]

Copying from #97

As far as I'm aware, higher tracks supersede lower tracks. For your example, I'd expect publishing to beta would also update users running older builds on internal. An I missing something?

Oh, I had always assumed the tracks were independent. I'll give it a shot on my next release.

[boswelja]

@amitav13 Were you able to confirm this behavior?

[boswelja]

Closing due to inactivity