Query Collection on Widget Issue

[vairagadeharshwardhan]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

I have a query on a widget. I filter the collection with an OR condition. When a new Firebase document is created, it shows the document, but when I delete the document in the Firebase it still shows the document on the UI and also in the debug panel. I can see the deleted document is coming up. It means it is not refreshing the data.

If I remove the or condition, it works as I expect it to work.

Expected Behavior

In the OR filter conditon also it should listen for document and collection changes.

Steps to Reproduce

Create Query Collection on a widget such as container. Give OR condition for filter and order the documents in date decreasing.
Create Firebase document, and delete any document manually or from client application. Check the debug data, if the backend query result show the expected data.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITESjMmB+cpgrsQF0LncacZqhQIgQ0QnU7gnlO1ucx43G7KsEYkyesmkNkNKT7y8TFZYIFmLhj4z//zTiezLD+0BISmqb7p80JVAczmXZFyjRcWoCbrhenxDL+hYBXWB0qaJqiRSJtdtcUY6wDqPNq3qNleeY8aSfxBlZ7vfcPo=

Visual documentation

Environment

- FlutterFlow version: 6.1.44
- Platform: Windows
- Browser name and version: NA
- Operating system and version affected: Windows 11 for the workstation

Additional Information

No response

[vairagadeharshwardhan]

[Alezanello]

Hello!

You’ll need to trigger a rebuild on the frontend, as the data is stored and cached there until it refreshes. When you perform a Delete Document action in FlutterFlow, you can use the Rebuild Page action to refresh the UI and load the updated data without the deleted document.

[vairagadeharshwardhan]

Yes I did that, rebuild the component, page, etc.
Even though the document is deleted in the backend and, restarted the app multiple times, it stays the same.

[Alezanello]

I’m sorry, but I wasn’t able to replicate this issue on my side. Could you please create a test project that reproduces the same situation? This will help us see which steps might be different from yours.