envman Variables passed from envman not working correctly

I have a build that is failing iOS provisioning due to envman:

project (ios/WellOne.xcworkspace) does not contain scheme: WellOneProductionRelease

It is failing because of the following shell script command that's run on step 2

echo "WellOneProductionRelease" | envman add --key IOS_P_SCHEME

This script is basically setting IOS_P_SCHEME to be WellOneProductionRelease which is the same exact value as what it was set to in the "Env Vars" section and whenever this line is commented the build works flawslessly although the variable should have the same value Please let me know how to resolve this, thanks!

Aug 23 '19 07:08 bassamseif

I was able to resolve the issue by just using the envman command differently as follows

envman add --key IOS_P_SCHEME --value "WellOneProductionRelease"

Although the two behaviors should basically be the same

Aug 28 '19 11:08 bassamseif

Hi @bassamseif!

Thanks for your report! Could you send us a build URL where this is happening in action?

Aug 30 '19 02:08 bitce

hi @bitce, here you go: https://app.bitrise.io/build/c978d4a09a7a4004#?tab=log

Aug 30 '19 12:08 bassamseif

Thanks, @bassamseif!

Can you let us know what made you expect this method:

echo "WellOneProductionRelease" | envman add --key IOS_P_SCHEME

To work just as well? Do you or did you find this documented anywhere?

Sep 02 '19 23:09 bitce

sure, in the readme here: https://github.com/bitrise-io/envman#usage-example-bash

Sep 03 '19 05:09 bassamseif

Completely right, thanks for pointing that out, we're taking a look at this 🙂

Sep 04 '19 08:09 bitce