Publishing in Google Play with dynamic track name

[StarK8912]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

Define a variable base on the current branch like:

- name: Set up Environment data
  script: |
    if [ $CM_BRANCH == "master" ] ; then
      export GOOGLE_PLAY_TRACK="production"
    else
      export GOOGLE_PLAY_TRACK="internal"
    fi

...

publishing:
    google_play:
        credentials: $GCLOUD_SERVICE_ACCOUNT_CREDENTIALS
        track: $GOOGLE_PLAY_TRACK

Expected results

Use the variable value to push the artifact to internal or production track

Actual results

Track "$GOOGLE_PLAY_TRACK" not found in Google Play

Build id (optional)

No response

[dam-ease]

Hello @StarK8912,
You need to use the environment section in YAML file to define GOOGLE_PLAY_TRACK as an environment variable that persists throughout the build process. Here is an example that should suit your use-case:

    environment:
      vars:
        GOOGLE_PLAY_TRACK: "default"
    scripts:
        - name: Set up Environment data
          script: |
            if [ "$CM_BRANCH" == "master" ] ; then
              echo "Setting track to production"
              echo "GOOGLE_PLAY_TRACK=default" >> $CM_ENV
            else
              echo "Setting track to internal"
              echo "GOOGLE_PLAY_TRACK=internal" >> $CM_ENV
            fi
    publishing:
      google_play:
        credentials: $GCLOUD_SERVICE_ACCOUNT_CREDENTIALS
        track: $GOOGLE_PLAY_TRACK

Let me know how this goes on your end.

[StarK8912]

@dam-ease It's working 🥳... The funny part, I already tried this approach but stopped the pipeline before it goes to the "publishing" step because the logs shown the variable with the previous value... weird...

My current solution:

environment:
      vars:
        GOOGLE_PLAY_TRACK: "default"
    scripts:
        - name: Set up Environment data
          script: |
            echo GOOGLE PLAY TRACK= "$GOOGLE_PLAY_TRACK"
            if [ "$CM_BRANCH" == "master" ] ; then
              echo LIVE ENVIRONMENT - MASTER
              DOMAIN="$DOMAIN_LIVE"
              echo "GOOGLE_PLAY_TRACK=production" >> $CM_ENV
            else
              echo DEV ENVIRONMENT - $CM_BRANCH
              echo "GOOGLE_PLAY_TRACK=internal" >> $CM_ENV
            fi
            echo GOOGLE PLAY TRACK= "$GOOGLE_PLAY_TRACK"
    publishing:
      google_play:
        credentials: $GCLOUD_SERVICE_ACCOUNT_CREDENTIALS
        track: $GOOGLE_PLAY_TRACK

The logs for step "Set up Environment data" are:

CM_BRANCH= develop
GOOGLE PLAY TRACK= default
DEV ENVIRONMENT - develop
GOOGLE PLAY TRACK= default

but anyway in the publishing step is using the correct "internal" value