Security vulnerabilities belong in our private security bug reporting process. Use this guide for ordinary bugs in the app.
A clear report helps us reproduce, diagnose, and fix a bug. Include screenshots, a short screen recording, or relevant logs and files where they add useful evidence.
Bug report template
Use a specific title, such as "Media upload stalls at 95%". Start with numbered steps that reproduce the bug. Include the exact clicks or taps, inputs, shortcuts, timing, and order.
State what you expected to happen, then describe what happened instead. Include the exact error or message shown. Open "User Settings", select the client information at the bottom of the sidebar, and paste the copied system and client details into the report.
Add evidence
Include only evidence that helps show or reproduce the issue. This may include screenshots, short videos, logs, sample files, or exports.
Protect privacy when sharing evidence
Screenshots and recordings can capture more than the bug. Check for other people's usernames, avatars, messages, open tabs, notification previews, and credentials shown in logs.
Before sending evidence, crop or blur unrelated chats, friend lists, and Community names. Search log files for email addresses, IP addresses, session tokens, and other people's user IDs, then conceal anything that is not required.
Prefer screenshots to photos because photos can contain EXIF metadata such as a location. Never include a session token, password, or authentication cookie. We do not need them to investigate a bug.
Submit your report
Email the completed report to bugs@fluxer.com. Use a concise, descriptive subject. You can instead open an issue in the Fluxer GitHub repository.
Security issues
If the issue may affect security, follow our security bug reporting process instead. Explain how to reproduce the issue, why it creates a security risk, and what impact you have identified. We will assess the report, coordinate a fix where needed, and discuss disclosure expectations with you.