A useful report explains what you expected, what happened, and how to reproduce it. Start with a test account and the smallest repeatable sequence.
Include the Flutex app version/build, API module version, Perfex/PHP versions, device model, operating system, and whether the build is debug or release. For build issues, include Flutter, Dart, Xcode or Android toolchain details as relevant.
Record the test time and timezone. Note the screen, action, request path, response status, and safe backend error code. For compilation failures, include the first actionable error and a short surrounding excerpt.
Useful developer commands include:
Capture output while reproducing the issue, then inspect it before sharing. Backend failures may also require the corresponding Perfex/PHP or web-server log excerpt.
Redact passwords, access/refresh tokens, Authorization headers, purchase codes, Firebase credentials, private keys, customer contact details, financial records, and attachment contents. Check screenshots as carefully as text logs.
State whether customer web login works, whether the config endpoint returns JSON, and whether the problem occurs in an unmodified release. List recent changes and avoid sending an entire unfiltered log archive when a short excerpt identifies the failure.