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
Generated obj-c class name is not changing after project name is changed in podfile #168
Comments
Try run |
Just tried ,it doesn't work, still EidolonKeys class is generated :( |
Is it possible it's doing both? |
No, the only one class generated is "EidolonKeys", nothing else. And even if I update the podfile with a new key e.g. plugin 'cocoapods-keys', { the new property "someOtherTestKey" is inserted in EidolonKeys class. So it definitely updates, only the class name remains the old one |
Try use Target as well then, it lets you specify the name
e.g.
|
I already tried it but didn't help either. |
I had the same issue today, and found out that changing the project name in the Podfile is not enough for cocoapods-key to pickup the new name, you have to change the name in the YAML file generated by cocoapods-key. Follow these steps to fix this problem:
The content of the file should look like this: ---
keys:
- Key1
- Key2
-....
path: [PATH_TO_YOUR_PROJECT_FOLDER]
name: [PROJECT_NAME]
|
@dfeddad solution worked for me. so did removing the YAML file from |
would it be possible to allow for the customizing of the name of the obfuscated class? |
Perfect, that was awesome, it worked like charm! |
When I started to use cocoapods-keys, for the first try I used the sample code to test, so I added Eidolon as project name.
Then a class was generated, correctly named "EidolonKeys" . Later I wanted to use the real name of my project so I changed it in the podfile:
After running either "pod install" or "pod update" still "EidolonKeys" class is generated instead of "MyProjectKeys". I would expect that the name of the generated class is always generated depending on the name which is defined in the podfile, in order to keep consistency with the ci and with other colleges who might be working on the same project. Am I doing something wrong, is it somehow possible to fix this issue?
The text was updated successfully, but these errors were encountered: