Reporting Issues

Thank you for helping to improve Cordova! Most issues for Apache Cordova are currently hosted at the Apache JIRA. However, we are starting to move issue management to GitHub.

Should I report an issue on JIRA or GitHub?

If the repository you are reporting an issue for has an Issues tab on GitHub, please report it there. Otherwise report it on JIRA.

Creating an issue on GitHub

Find the repository of the component which your issue applies to. To figure out which repository to report your issue to, you can take a look at the full list of Cordova repositories. Some of the most popular repositories are:

Once you have found the correct repository to create your issue in, go to the Issues tab, and click New issue. Simply fill out the issue template, and submit your issue. If there is no Issues tab, please report the issue on JIRA instead.

Creating an issue in JIRA

A JIRA account is required before you can submit issues (you can easily create one here). Before submitting an issue, please take a moment to search JIRA to see if an issue already exists. If it does, please consider commenting or voting for the issue to help raise its visibility.

Once you have created an account and logged in, click the blue "Create" button at the top of the Cordova JIRA page to create an issue. In the dialog that appears, please fill out the following fields to the best of your ability. All fields besides those listed here can be left blank.

Field Description
Project Make sure that Apache Cordova is selected
Issue Type Whether or not this is a bug or feature request
Summary A one line description of the issue
Component The part of Cordova this issue pertains to. Please select only one component if possible (e.g. if you find a bug while using cordova-plugin-camera in Android, select the "Plugin Camera" component and not "Android")
Affects Version The version of the component that this issue pertains to
Environment Some extra context about the environment in which a bug was found (e.g. the version of Android you are running, your version of the Cordova CLI, your development platform, etc.)
Description A thorough description of the issue. For bugs, please provide code (using github) or steps for reproduction as well as any device logs or stack traces you might have.
Labels Please label your issue with the platform it affects (e.g. ios, windows, android, etc.). Include other relevant labels such as regression, easyfix, bug, dev, staging, production, discussion, question, security, legal, enhancement, production, and/or feature.
Priority The impact of the issue (see below)

Issue Priority

We gauge issue priority on the following scale:

If you aren't sure about the priority, leave the default (major) selected. Please be aware that as our contributors triage issues, they may change the priority based on our criteria.

Finding out versions

You can quickly find out versions of platforms/plugins you're using by running:

cordova platform ls


cordova plugin ls

in your project respectively. You can find out the version of the Cordova CLI you're using by running:

cordova --version

Generating CLI logs

You can use --verbose flag to generate detailed logs for cordova build-time bugs related with the CLI. This helps significantly in debugging.