Bug Reports¶
Submitting accurate bug reports ensures maintainers can quickly identify and fix issues.
Check the Issue Tracker
Always search the GitHub Issues page before creating a new report. If an issue already exists for your bug, simply leave a comment or reaction to confirm it.
Creating a Report¶
Head over to our New Issue page. A good bug report presents maintainers with a clear path to reproduce the problem.
Provide a descriptive title for your issue and include the following details in the body:
Description¶
Explain the bug succinctly. Provide context regarding what the application was doing before the crash or unexpected layout occurred.
## Description
The application crashes when tapping the "Change Language"
button directly after completing a download.
Steps to Reproduce¶
The most critical element of the report. List the exact sequence of actions needed to trigger the bug.
## Steps to Reproduce
1. Open the application.
2. Navigate to 'Settings'.
3. Tap on 'Change Language'.
4. Note the app closes instantly.
Expected Behavior¶
Contrast the expected outcome against the actual outcome.
## Expected Behavior
A dialog prompt listing available languages should appear.
## Actual Behavior
The application closes immediately (crashes).
Environment¶
Bugs often rely on specific hardware or architectures. Append your environment details.
Visual Evidence
If the issue refers to a visual glitch or layout anomaly, drag-and-drop screenshots or a short video clip directly into the GitHub text editor. Pictures drastically reduce diagnosis time.