If a Bitrise script step sees your env var literally instead of its value, check your quotes. Single-quoted Bash strings do not expand variables; use double quotes around anything that references one.

Context: From a Bitrise Discuss forum thread. Environment variables used inside a script step did not expand because the payload was wrapped in single quotes in Bash, which prevents expansion. Switching to double quotes fixed it. The thread is a classic reminder that the quoting belongs to the shell, not to Bitrise.