When running in CI, we've opted to just run the pod keys generate command rather than pod install to generate the obfuscated objc files. However, as we're using ENV keys to set the values there aren't any keyring yaml files that contains the name of the keys and as such the command doesn't know the name of the ENV variables to look for.
The solution
Add an option --keys to the generate command that's used to create a runtime keyring if no existing keyring could be found, letting the system know which keys to look for.
export Foo=foo
export Bar=bar
pod keys generate --keys=Foo,Bar
The problem
When running in CI, we've opted to just run the
pod keys generate
command rather thanpod install
to generate the obfuscated objc files. However, as we're using ENV keys to set the values there aren't any keyring yaml files that contains the name of the keys and as such the command doesn't know the name of the ENV variables to look for.The solution
Add an option
--keys
to the generate command that's used to create a runtime keyring if no existing keyring could be found, letting the system know which keys to look for.