Passing an override for an environment variable on manually started build not working

Question & Answer
1

Hi all, this has been driving me nuts all afternoon. I have a workflow which creates an XArchive for uploading to TestFlight. I want to be able to change the Xcode configuration when I trigger the workflow manually.

So the first thing I did was create a variable in the environment are like this:

Workflows:
    testflight:
        steps:
        - xcode-archive@2:
            inputs:
            - project_path: "$BITRISE_PROJECT_PATH"
            - scheme: "$BITRISE_SCHEME"
            - force_team_id: ''
            - force_code_sign_identity: ''
            - force_provisioning_profile: ''
            - force_provisioning_profile_specifier: ''
            - configuration: "$XCODE_CONFIGURATION"
            - export_method: "$BITRISE_EXPORT_METHOD"
        envs:
            - XCODE_CONFIGURATION: Release
                opts:
                    is_expand: false

(Please excuse if that’s not quite formatted correctly, I hacked out all the other stuff in the workflow)

Now when I run the workflow I see the configuration of the XArchive step set to Release.

I then tried running the workflow again, but this time passing XCODE_CONFIGURATION set to Debug like this:

{
    "branch":"develop",
    "workflow_id":"testflight",
    "environments":[{
        "mapped_to":"XCODE_CONFIGURATION",
        "value":"Debug",
        "is_expand":false
    }]
}

But when the flow ran, it still showed XArchive configuration as Release.

I’ve tried all sorts of things and I can’t figure out why this is not working. Any clues?

2

Hi @Drekka-IAG!

Sorry to hear about the issue! Can you please paste a build URL here where you tried to overwrite the original value? Thanks!

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.