Ticket requirements and response process

Use the support route linked from the Flutex CodeCanyon item page. Check existing knowledge-base articles first, then submit one clear report per distinct issue.

Include these details

Subject: Short description of the problem
App version/build:
API module version:
Perfex and PHP versions:
Device and operating system:
Flutter/Xcode/Android toolchain, if relevant:
Debug or release build:
Steps to reproduce:
Expected result:
Actual result:
First relevant error or safe API error code:
Time and timezone of the test:
Recent customizations or updates:
Checks already completed:

Attach a sanitized screenshot or short log excerpt when it helps explain the failure. For connection issues, state whether the public config endpoint and customer web login work. For notification issues, state whether the app was open or in the background and whether a direct Firebase test succeeds.

Protect your installation

Never send passwords, production access tokens, private keys, or full customer datasets in the initial report. Provide purchase verification only through the designated private process. If temporary access is later needed, agree on a limited test account and revoke it when the work is finished.

Keep follow-up details in the same support conversation so the investigation has one history. Response availability and any service commitments are those published by the author; this article does not create a separate response-time guarantee.


Write Your Comment