Supabase Streaming Cache Issue

[mokaPotter]

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 simple chats page, for desktop screen size. The chat_list is on the left, and chat_messages on the right.

All the chats in the chat_list have a property_ref that joins them all to the same property. This is also my unique key for caching.

When a user is viewing property A's chats, and then navigates to property B, and then views property B's chats, the user is still viewing the cache from property A's chat_list.

**This caching method was working when I had a single time query for chat_list. Upon changing it to a stream, it began to bug

Expected Behavior

A user views property A's chat_list, navigates to property B, then views property B's chat_list, and immediately sees the chat_list for property B.

Steps to Reproduce

1. Create a page that has a list of different properties (ie. locations)

2. Each of these properties is to have a unique key

3. Upon selecting this property, update app state propertyId, to be the Primary key for this property.

4. Create another page that has a chat_list.

5. Each of the items in this chat_list is to have a property_ref Foreign key that is linked to a particular property

6. Filter the chat_list query by property_ref = app state propertyId

7. Cache the chat_list with the unique key being the propertyId app state

8. make sure chat_list query is a stream query

9. Navigate between different properties which should each have a few rows in chat_list

10. Observe that the cache isn't working correctly

11. Change chat_list from stream to single time query, observe that caching is working correctly

Reproducible from Blank

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

Bug Report Code (Required)

IT40h/Hfz5RIrul77s3uSPlX/SYmNVh+W5MvrtV7aCgofePtOol3evWkdlJWYO2oS1FMIkSmmmozw/Twi+LtMsA4YCmtGZw/zZNiTAvLQk6Qe5OBBqjpPmt5BZhbGUy51p+rmyVdOrJeSUIH3FOPfvOiYAjaQIC0IlFISq/LZO4=

Visual documentation

Screen.Recording.2025-03-13.at.8.53.48.AM.mov

Environment

- FlutterFlow version: Version 5.2.8 (5.2.8)
- Platform: Web (desktop)

- Browser name and version: 
Chrome (Version 133.0.6943.143 (Official Build) (arm64))
DuckduckGo (Version 1.121.0 (340))

- Operating system and version affected: MacOS Sonoma 14.6.1 (23G93)

Additional Information

This caching method was working as a single time query, as a stream, started bugging.

Already submitted in the community channel:
https://community.flutterflow.io/ask-the-community/post/supabase-steam-query-problems-onSWGiVD1ePt8TD?highlight=4fj1Ac7d9FvbAc7

[Juansarmi]

Hello,

I noticed that you've opened another ticket with more details.

To keep everything organized and avoid duplicates, I’ll proceed with closing this one so we can track updates in the other thread: #5555

Best regards.

[mokaPotter]

Ok no worries Juansarmi, as they were separate bugs I thought a separate ticket was required. All good if you prefer a single thread

[github-actions]

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.