Skip to content

Troubleshooting Guide Topics: divided the contents in https://docs.flutterflow.io/troubleshooting i… #444

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 13, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,5 @@ When you download your project from FlutterFlow and run it locally in your IDE,

If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](/testing/local-run/#4-running-app-on-device). ​By following these steps, you can fix the errors that you face after downloading the code and run locally.

If you continue to experience issues, contact the FlutterFlow support team via live chat or email at [email protected].




If you continue to experience issues, contact the FlutterFlow support team via live chat or email at [email protected].
4 changes: 2 additions & 2 deletions docs/troubleshooting/deployment/run_mode_build_failure.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,12 +92,12 @@ This guide provides a structured approach to troubleshooting and resolving "Run
- **Utilize local debugging**:

If the error is elusive, running the debugger locally on your downloaded code can help identify the issue.

- **Leverage browser tools**:

The browser's console and developer tools can offer insights, especially when dealing with errors that don't manifest in traditional debug outputs.


:::info[Additional Resources]
[Basic Troubleshooting Guide – FlutterFlow Documentation](https://docs.flutterflow.io/troubleshooting/basic-troubleshooting-guide)
:::
:::
8 changes: 3 additions & 5 deletions docs/troubleshooting/index.md
Original file line number Diff line number Diff line change
@@ -1,17 +1,15 @@
---
slug: /troubleshooting
title: Troubleshooting Guide
title: Detecting Issues
description: A guide to troubleshoot or debug issues that occur within FlutterFlow project.
tags: [Troubleshooting]
sidebar_position: 0
keywords: [Troubleshooting, Debugging, Detect Issues, Runtime Errors]
---

# Troubleshooting Guide
# Detecting Issues

This is a general troubleshooting guide for any issues that occur within FlutterFlow projects.

## Detecting issues
This is a general troubleshooting guide for detecting any issues that occur within FlutterFlow projects.

We've improved our issue detection capabilities and added features to provide clearer insights into what might be causing these problems. Here are some options you can use to troubleshoot the issue.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,9 @@ This error is typically triggered when:

Example:

- If Firestore rules are configured as:
- If Firestore rules are configured as:

```js
```js
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
Expand All @@ -37,15 +37,14 @@ This error is typically triggered when:
}
}
```

Any Firestore query will fail because no read or write access is allowed.

- If rules allow only authenticated access:

```js
```js
allow read, write: if request.auth != null;
```

```
And a query is placed on a page before the user signs in (e.g., on the login screen), it will trigger this error.

Descriptive widget names can help you quickly identify which query or widget is triggering the permission issue. In the example above, the error message references a widget named Container. Renaming it to something like UserQueryContainer can make debugging easier.
Expand Down
8 changes: 4 additions & 4 deletions docs/troubleshooting/test-mode/gray_screen_run_mode.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Seeing a gray screen in Run Mode usually points to a configuration issue in your

1. **Check Firebase Permissions**

Ensure that `[email protected]` has the following roles:
Ensure that [email protected] has the following roles:

- **Editor**
- **Cloud Functions Admin**
Expand All @@ -26,7 +26,7 @@ Seeing a gray screen in Run Mode usually points to a configuration issue in your
1. Go to the **Firebase Console**.
2. Select your project → **Project Overview**.
3. Navigate to **Users and permissions** → **Advanced permissions**.
4. Locate `[email protected]` and ensure it has the roles listed above.
4. Locate [email protected] and ensure it has the roles listed above.

![](../assets/20250430121529462395.png)

Expand Down Expand Up @@ -81,7 +81,7 @@ Seeing a gray screen in Run Mode usually points to a configuration issue in your

7. **Refresh FlutterFlow Environment**

- Press `Ctrl + R` (Windows) or `Cmd + R` (Mac) to refresh FlutterFlow.
- Press Ctrl + R (Windows) or Cmd + R (Mac) to refresh FlutterFlow.
- Clear your browser cache.
- Log out and back in.

Expand All @@ -100,4 +100,4 @@ Seeing a gray screen in Run Mode usually points to a configuration issue in your
:::info[Additional Resources]
- **[Run Flutter App Locally](/testing/local-run)**
- **[FlutterFlow Firebase Integration Guide](/integrations/firebase/connect-to-firebase/#step-1-set-up-your-project)**
:::
:::
2 changes: 1 addition & 1 deletion docs/troubleshooting/test-mode/slow_test_mode_load.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,4 +47,4 @@ If the issue persists after following the steps above, check the
**[official support](https://intercom.help/flutterflow/en/articles/7052737-test-mode-is-not-loading-or-is-very-slow-it-takes-a-long-time-to-load-the-app)** article.
:::

Following these steps should resolve most Test Mode performance issues and reduce load times for future previews.
Following these steps should resolve most Test Mode performance issues and reduce load times for future previews.