```
). That increases the readability. Bonus points for applying the appropriate syntax highlighting. (Tip: Podfiles are written in a Ruby DSL.)In short, since you are most likely a developer, provide a ticket that you yourself would like to receive.
We are not here to support your individual projects. We depend on you (the community) to contribute in making the tool better for everyone. So debug and reduce your own issues before creating a ticket and let us know of all the things you tried and their outcome. This applies double if you cannot share a reproduction with us because of internal company policies.
First check if you are using the latest CocoaPods version before filing a ticket. You can install the latest version with $ [sudo] gem install cocoapods
.
Then check if the same problem applies with the same Podfile but in a completely new and empty application Xcode project, thus excluding whether or not there is an issue with conflicting settings.
Please include steps to reproduce and all other relevant information, including the version of CocoaPods and any template printed by the tool.
If questions in the error template are left unanswered, the issue will be closed as a bad bug report.
If there is a regression in the projects generated by CocoaPods please include the output (redacted if needed) of one of the following commands:
$ xcodeproj target-diff $ xcodeproj project-diff
If you are familiar with Ruby, making a pull request with a failing test case can speed up the resolution of the bug. If the issue is more complex you can add an integration test which doesn't require any ruby knowledge.
Please try to be precise about the proposed outcome of the feature and how it would related to existing features.
From the CocoaPods blog:
Fighting feature creep in CocoaPods is not easy. We hear about a lot of great ideas and many of them don't make the cut as they would not be useful for at least 80% of our users.
Should you require a feature isn't suited for mainstream users, consider suggesting a CocoaPods plugin instead.
We love pull requests and if a contribution is significant we tend to offer push access. We suggest you take a look at our Contributing guide for info on development setup, and some of our best practices.
All contributions will be licensed under the MIT license.
Code/comments should adhere to the following rules:
[Installer] install pods
).If you made it all the way to the end, bravo dear user, we love you. You can include this emoji in the top of your ticket to signal to us that you did in fact read this file and are trying to conform to it as best as possible: 🌈