Reporting a bug
How to file clear, high-quality bug reports for Fluxer Support or our GitHub.
Last updated February 16, 2026
Use this guide to share a clear report so we can reproduce and fix the bug quickly. Screenshots, short screen recordings, and relevant logs or files help us diagnose the issue faster.
Bug report template
Title: Be specific, e.g., Media upload stalls at 95%.
Steps to reproduce:
- Step one (include exact clicks/taps, inputs, or shortcuts).
- Step two.
- Step three (note timing or ordering details).
Expected result: What you expected to happen.
Actual result: What happened instead (include exact errors or on-screen messages).
System and client settings: In User Settings, tap your client info at the bottom of the sidebar to copy it, then paste it here.
Add evidence
Include anything that shows the issue: screenshots, short videos, logs, or sample files/exports. The more specific your report is, the faster we can help.
Submit your report
Email support@fluxer.app with the completed template. A concise but descriptive subject line helps us triage quickly. If you prefer GitHub, you're welcome to file issues in the Fluxer GitHub repository.
Security issues
If you believe the issue is security-related, visit our Security bug bounty page instead of emailing support. Follow the guidance there and include clear steps, why you believe it's a security risk, and any impact you've identified. We respond quickly to assess the report, coordinate a fix, and discuss disclosure expectations.