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

Keys not being generated when using env file #212

Open
ryoustra opened this issue Dec 7, 2020 · 3 comments
Open

Keys not being generated when using env file #212

ryoustra opened this issue Dec 7, 2020 · 3 comments

Comments

@ryoustra
Copy link

ryoustra commented Dec 7, 2020

I'm attempting to use this with a Swift project in Xcode, with both macOS and iOS targets.

Ideally, I'd have the keys in an env file, but that appears not to work. When the keys are not included in .env, pod install prompts for values, and generates the code correctly while inserting keys in the keychain. All good.

If I use the pod to remove the key (or simply add a new one), clear out derived data, build clean, but then add the key to the .env file, pod install will no longer prompt for a value (as expected) but the code is not generated correctly - i.e., no key names/values are added to the Keys class. Running pod keys confirms that none were generated.

Any reason to consider why this might not be working? It seems that I've isolated the issue cleanly enough, but if it's working for others, there's clearly something else at play.

@orta
Copy link
Owner

orta commented Mar 4, 2021

No idea

@vanthanhtran245
Copy link

vanthanhtran245 commented May 24, 2021

@ryoustra Try with run cmd rm -rf ~/.cocoapods/keys and pod install again

@rogerluan
Copy link
Contributor

rogerluan commented Sep 27, 2021

Thanks @vanthanhtran245 , that command was the solution for a problem I was facing 👍 here, keys I was populating in the Podfile weren't being generated in the .h file, only the keys that were present in that ~/.cocoapods/keys/….yaml cache was being generated in the .h file and I didn't understand why 😬

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

4 participants