CONTRIBUTING.md

Contributing

1. Create an issue to make sure its something that should be done.

Before submitting a Github issue, please make sure to

• Search for existing Github issues
• Review our Help Center
• Read our docs.revenuecat.com

Common project specific issues

There are certain project specific issues that are commonly misinterpreted as bugs.

• Offerings, products, or available packages are empty
• Invalid Play Store credentials errors
• Unable to connect to the App Store (STORE_PROBLEM) errors

For support I'd recommend our online community, StackOverflow and/or Help Center 👍

If you have a clearly defined bug (with a Minimal, Complete, and Reproducible example) that is not specific to your project, follow the steps in the GitHub Issue template to file it with RevenueCat without removing any of the steps. For SDK-related bugs, make sure they can be reproduced on a physical device, not a simulator (there are simulator-specific problems that prevent purchases from working).

2. Create a fork/branch.

3. Do your work.

Be sure to adhere to the prevailing style of the project.

4. Write tests for your fix/new functionality.

5. Create a pull request to revenuecat/master and request review

Explain in your pull request the work that was done, the reasoning, and that tests passed.

6. Make changes in response to review

7. Bask in the glory of community maintained software