Submit Bug Reports

This page guides you on submitting the bug reports in the GitHub issue tracker.

We have created a GitHub repository specifically dedicated to tracking bug reports from our community of users. By doing so, we aim to foster a more open and collaborative relationship with our users, encouraging them to report any bugs or glitches they encounter while using FlutterFlow.

This will enable us to track, triage, and resolve issues in a timely and efficient manner. So, if you encounter any bugs or issues, please don't hesitate to report them to us on our GitHub repository! 🐛

You should use this only for reporting FlutterFlow bugs and improvements/addition to the Documentation.
Any new features, suggestions, and questions should be discussed in the community or submitted through our user feedback form.

Here is the simple flow you can refer to submit the bug report:

Before creating a new issue, it's recommended to search the issue tracker to avoid submitting duplicate reports. If you find an existing issue, show your support by upvoting it using the Thumbs Up icon. If you have additional information to share or clarifications to make, add them as comments on the original issue. In case you can't find the relevant issue, you can create a new one with all the necessary details. This will help us address the issue faster and more efficiently.

Here are the step-by-step instructions:

Open the issue tracker and click on the New Issue button. Note: If you haven't already, you must create a GitHub account.

On the right side of the Bug Report, click the Get Started button.

When describing your issue in the Title box, be as specific and concise as possible. Use descriptive words that accurately convey the problem. For example, instead of simply writing "DatePicker issue," provide more details such as "Disabled future dates in the Date/Time picker action, still shows".

This will help us and others quickly understand the issue and can also help with searchability in case someone else has experienced the same problem.

If your issue doesn't exist and you allow us to access your project for the sole purpose of investigation, you can tick both checkboxes.

In the 'Current behavior' section, provide as much detail as possible about the behavior you are experiencing.

In the 'Expected behavior' section and enter a clear and concise description of what you expected to happen.

Make sure that the expected behavior is realistic and achievable.

In 'Steps to Reproduce' section, write the step-by-step instructions to reproduce the bug. Also, mention any specific settings or configurations that might be relevant. This will help us diagnose the issue. Note: Issues cannot be accepted if they are too vague. For example, "project fails to build."

The 'Bug Report Code' is a unique code that helps us assess your issue. To copy it, open the Widget Tree > Right Click > select Get Bug Report Code and paste it here. Note that if an error is related to a specific widget, select the widget, right click and get the code.

Use the 'Context' section to describe how it has affected you and what you are trying to accomplish.
In 'Additional Info' you can provide a screenshot or recording, links, references, or anything else that will give us more context about the issue you are encountering.