Skip to content

Supabase Streaming for ListView stops streaming with a single filter #4903

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

Closed
2 tasks done
the-digital-pro opened this issue Nov 15, 2024 · 7 comments
Closed
2 tasks done
Assignees
Labels
Bug Cherry Pick status: confirmed Issue has been reproduced and confirmed as a bug.

Comments

@the-digital-pro
Copy link

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

Simple ListView which has a non-single query. Without a filter streaming works perfectly. As soon as I add a filter. i.e booked=true realtime updates do not update.

Expected Behavior

I would expect to see the ListView updated with any changes within the realtime Supabase database.

Steps to Reproduce

  1. Setup Supabase project and table with sample data
  2. Enable realtime on your table
  3. Setup FlutterFlow for Supabase v2
  4. Add a ListView
  5. Add a query and filter on 1 table column
  6. Delete row in the database

Reproducible from Blank

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

Bug Report Code (Required)

IT9XiuflxIt1pbxK0KX6cfpviiovIjt9RLxMm9V+ZwsdCLbqBI13P/TBTFFWWbS/T2w7IWGN+WcepqyOvdrIMeY5HxeWfLZm+c9ASQCVJWOWbJSJErWJPmJ/J+hhflS/yre3pgpCWepucVIi7XGQAunKFyvaMLnhIkczAMqaOdjU+VKYLSTrMTpZwW07HxPXBtgcZhOxxJPK6asBlI/S/ol8qBVXzoPSwtX1TBKTWVk=

Visual documentation

No visual needed

Environment

- FlutterFlow version: 5.0.12
- Platform: Mac M3 Pro
- Browser name and version: Google Crome but using Local Run ios Simulator
- Operating system and version affected: Sequioa 15.0.1

Additional Information

No response

@the-digital-pro the-digital-pro added the status: needs triage A potential issue that has not been confirmed as a bug. label Nov 15, 2024
@the-digital-pro
Copy link
Author

Just want to add that I am seeing no errors. It simply just does not update.

@jakals37
Copy link

I have same issue.

@SlvrB
Copy link

SlvrB commented Nov 15, 2024

I have same issue

@Alezanello Alezanello self-assigned this Nov 15, 2024
Copy link
Collaborator

I can confirm this issue and will escalate it to the engineering team for a fix.

@Alezanello Alezanello removed the status: needs triage A potential issue that has not been confirmed as a bug. label Nov 15, 2024
@Alezanello Alezanello added status: confirmed Issue has been reproduced and confirmed as a bug. Bug labels Nov 15, 2024 — with Linear
@Alezanello Alezanello removed their assignment Nov 15, 2024
@glgh
Copy link
Collaborator

glgh commented Nov 18, 2024

hi @the-digital-pro - does this happen only when deleting an existing row, but not when inserting a new row? If so this is a known limitation with the Supabase streaming API: Delete events are not filterable.

@glgh glgh closed this as completed Nov 18, 2024
@the-digital-pro
Copy link
Author

@glgh I'm puzzled to why you have closed this issue. If I have a row in my database which is boolean and it is set to true. InFF, I have a standard filter on my query which returns back all records that are true then you would expect to see these in your listview. If I then go in Supabase and mark one of these records as FALSE you would expect to see this one record removed from the ListView. This is not the case. It remains there.

@glgh
Copy link
Collaborator

glgh commented Nov 19, 2024

hi @the-digital-pro, I appreciate the detail you shared - unfortunately this is a supabase streaming API limitation and it affects both 1) deleting rows and 2) updating rows such that it no longer meets the filter condition (<- this part is not clearly documented unfortunately) -- in each case the row would remain even though the expected behavior is it will go away. This also affects both their stream API and realtime channel API in our internal testing.

This is only a limitation when filters are enabled -- without filters it should work fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Cherry Pick status: confirmed Issue has been reproduced and confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

6 participants