Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variables passed from envman not working correctly #175

Open
bassamseif opened this issue Aug 23, 2019 · 6 comments
Open

Variables passed from envman not working correctly #175

bassamseif opened this issue Aug 23, 2019 · 6 comments

Comments

@bassamseif
Copy link

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!

@bassamseif
Copy link
Author

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

@bitce
Copy link

bitce commented Aug 30, 2019

Hi @bassamseif!

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

@bassamseif
Copy link
Author

@bitce
Copy link

bitce commented Sep 2, 2019

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?

@bassamseif
Copy link
Author

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

@bitce
Copy link

bitce commented Sep 4, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants