Skip to content

Commit dc308ad

Browse files
committed
improved formatting, updated content
1 parent 4aae8ed commit dc308ad

7 files changed

+212
-197
lines changed

docs/troubleshooting/backend-issues/backend_call_update_document_action_is_not_working.md

Lines changed: 0 additions & 61 deletions
This file was deleted.

docs/troubleshooting/backend-issues/backend_issues.md

Lines changed: 0 additions & 36 deletions
This file was deleted.

docs/troubleshooting/backend-issues/backend_query_is_failing_and_my_list_shows_a_gray_box_instead_of_a_list_of_items_I_get_a_red_screen_in_test_mode..md

Lines changed: 0 additions & 86 deletions
This file was deleted.
Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,30 @@
11
---
22
keywords: ['listview', 'returning', 'only']
33
slug: /my-listview-is-only-returning-one-item
4-
title: My listview is only returning one item
4+
title: My ListView Is Only Returning One Item
55
---
6-
# My listview is only returning one item
6+
# My ListView Is Only Returning One Item
77

8+
If your **ListView** is only returning one item in FlutterFlow, check the following possible causes:
89

9-
## Things to check if you listview is only returning one item
10+
- **Use a Dynamic Widget**
1011

11-
Here are the things to check if you are facing this issue:
12+
Ensure you are using a dynamic widget such as **ListView**, **GridView**, **Row**, or **Column** to dynamically generate multiple children.
1213

13-
## - Use a dynamic widget
14+
- **Query for a List**
1415

15-
Make sure you are using a **ListView**, **GridView**, **Row**, or **Column** to dynamically generate the children.
16+
Confirm that your query retrieves a **list of documents** rather than a single record.
1617

17-
## - Query for a list
18-
Ensure your query is for a **list of documents** and not a single record.
18+
- **Check Filters**
1919

20-
## - Check filters
21-
If you are using a filter, make sure the data present in Firestore has **more than one record** that can pass through the filter.
20+
If you're applying filters, make sure that your Firestore database contains **multiple records** that satisfy the filter conditions.
2221

23-
## - Sufficient records
24-
Make sure that your Firestore collection has **enough records**.
22+
- **Sufficient Records**
2523

26-
## - ListType field
24+
Verify that your Firestore collection has **enough records** to display multiple items.
2725

28-
If you are querying a single field, make sure it’s a **ListType field** in both FlutterFlow and Firebase.
26+
- **List Type Field**
2927

28+
If you are querying a single field, ensure that it’s defined as a **ListType field** in both FlutterFlow and Firebase.
3029

30+
By carefully reviewing these areas, you should be able to resolve the issue of your ListView returning only one item.
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
keywords: ['backend', 'issues', 'troubleshooting']
3+
slug: /troubleshooting-backend-issues-in-flutterflow
4+
title: Troubleshooting Backend Issues in FlutterFlow
5+
---
6+
# Troubleshooting Backend Issues in FlutterFlow
7+
8+
If you are facing issues related to the backend in FlutterFlow, follow these steps to ensure your Firebase setup is correctly configured:
9+
10+
- **Add Proper Cloud Permissions**
11+
12+
Grant the following permissions to **[email protected]** in your Firebase project:
13+
14+
- **Editor**
15+
- **Cloud Functions Admin**
16+
- **Service Account User**
17+
18+
**[Learn how to assign Firebase permissions.](/integrations/firebase/connect-to-firebase/#allow-flutterflow-to-access-your-project)**.
19+
20+
- **Update Firebase Rules**
21+
22+
Ensure that your Firebase Firestore security rules are updated correctly.
23+
24+
**[See how to update Firebase rules.](/integrations/database/cloud-firestore/firestore-rules/)**.
25+
26+
After updating the rules, delete **[email protected]** from your authenticated users, redeploy the Firestore rules, and validate the schema again.
27+
28+
![](../assets/20250430121532523511.png)
29+
30+
- **Match Data Field Types and Names**
31+
32+
Verify that all data field types and field names match between **Firestore** and **FlutterFlow**.
33+
34+
- **Validate Firestore Schema**
35+
36+
Use the **Validate** button in **Firestore → Settings** inside FlutterFlow to confirm that the Firestore collection schema matches the FlutterFlow configuration.
37+
38+
![](../assets/20250430121532793176.png)
39+
40+
- **Reset Firebase Setup (If Needed)**
41+
42+
If you have already completed the Firebase setup but continue to experience issues, remove existing permissions and complete the setup process from scratch.
43+
44+
**[Follow Firebase setup instructions.](/integrations/firebase/connect-to-firebase/)**.
45+
46+
- **Authorized Domains**
47+
48+
Add `app.flutterflow.io` to your **Authorized Domains** under the **Authentication** tab in Firebase.
49+
50+
- **Refresh FlutterFlow**
51+
52+
Make sure you are using the latest version of FlutterFlow:
53+
54+
- Press **Ctrl/Cmd + Shift + R** to refresh.
55+
- Clear your browser cache.
56+
- Log out and back into FlutterFlow.
57+
58+
- **Use Blaze Plan for Cloud Functions**
59+
60+
To use Cloud Functions like Push Notifications, Payments, and other features, ensure your Firebase project is on the **Blaze Plan**.
61+
62+
By following these steps, most backend issues in FlutterFlow can be resolved effectively.
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
keywords: ['call', 'document', 'backend']
3+
slug: /update-document-action-fails-during-backend-call
4+
title: Backend Call Update Document Action Not Working
5+
---
6+
# Backend Call Update Document Action Not Working
7+
8+
When performing the **Update Document** action, you may encounter a situation where the loading indicator appears but then stops without completing the action. This indicates that the update was unsuccessful. If the update succeeds, the next steps in your action flow, such as displaying an alert dialog, should execute automatically.
9+
10+
![](../assets/20250430121241690449.gif)
11+
12+
![](../assets/20250430121241899370.png)
13+
14+
:::note
15+
After performing the update action, always verify that the data has been correctly updated in your database. If your document is not streamed in real-time within your app, the updated data may not immediately appear. Check the data in FlutterFlow CMS or directly in Firebase to confirm the update.
16+
:::
17+
18+
**Why Does Updating a Document Fail?**
19+
20+
When the update action fails, the action flow stops, preventing any subsequent actions from executing.
21+
22+
There are two common reasons why the update action may fail:
23+
24+
1. **Permission Issue in Firestore**
25+
26+
The user may not have the necessary permission to write to the document.
27+
28+
![](../assets/20250430121242149430.png)
29+
30+
**Cause:**
31+
The Firestore security rules may not allow the current user to write (edit) documents.
32+
33+
**Solution:**
34+
Review and configure your Firestore rules to grant write permission. For example, allowing write access to authenticated users is often sufficient if your app requires user authentication.
35+
36+
2. **Data Type Mismatch**
37+
38+
The values you are attempting to write may not match the expected field types.
39+
40+
For example, assigning a string value to a field that expects an integer will result in failure.
41+
42+
![](../assets/20250430121242530889.png)
43+
44+
**Cause:**
45+
Attempting to write a value of the wrong type, such as assigning text to a number field.
46+
47+
**Solution:**
48+
Verify that the values being written match the expected data types for each field. If the data comes from an API call or form input, consider using custom actions to convert the value to the appropriate type before performing the update.
49+
50+
:::note
51+
If you want to save a text field value as a number, ensure that the text field input type is set to **Number**.
52+
:::
53+
54+
:::info[Additional Troubleshooting]
55+
You can check for error details in your browser's developer console (F12). For example, permission errors will typically appear in the console logs, as shown below:
56+
57+
![](../assets/20250430121242814005.png)
58+
:::

0 commit comments

Comments
 (0)