Reporting an issue

A useful report

Use this structure when preparing an issue:

Product and version:
Operating system / device / editor:
Expected result:
Actual result:
Steps to reproduce:
Frequency:
Relevant, redacted logs:

A small, repeatable example is often more useful than a complete project. Include a screenshot only when it explains the issue, and remove private information first.

What to leave out

Do not share passwords, access tokens, session cookies, private keys, purchase receipts containing personal information, or unredacted account identifiers. Avoid publishing another person’s information.

Support channels

Email [email protected] with the report. Include the product name in the subject. For a purchase problem, use purchase help and send the store order reference privately.

Community discussion can be useful for general questions. Keep receipts and personal information out of public channels. Use [email protected] for a suspected vulnerability.

Privacy requests

For access or deletion questions, email [email protected] and read privacy help. Never post identity documents in a public issue.