From the error, it looks like there is an issue with the way the filter is being applied.
Try using the following filter:
.eq("user_id", SupabaseAuth A's User ID:lowercase:formatted as JSON-safe)
.not("brand_name", "in", [RepeatingGroup_Collab's [SB] selected_brands:each item:lowercase:formatted as JSON-safe])
Ensure that you’re passing an array (like the one you’re creating from your repeating group) and the values are properly formatted as JSON-safe.
Additionally, verify that the field brand_name contains valid data for comparison.
this is what i have in the table, so the expected action from that previous test would be all the red box entries to be deleted with the DELETE action:
I have a quick question regarding the Supabase Pro Kit plugin for Bubble. I’m currently working with the Bubble Native Mobile environment, and I’ve noticed that some of the plugin’s functionalities seem to work only on the web version of the app.
Could you please clarify:
Are there any plans to make the plugin compatible with Bubble’s native mobile environment?
If so, is there an estimated timeline for this support?
steven.h.liu.1,
We would greatly appreciate it if you could follow these steps, as they will help us better understand the root of the problem:
Print out a text element on your page with the following content: RepeatingGroup_Collab's [SB] selected_brands:each item:lowercase:formatted as JSON-safe. This will allow us to see what value is being passed into your filter.
Test with hardcoded values: Try executing the workflow with hardcoded values, for example: .not("brand_name", "in", ['Instagram', 'samsung']). This will help us check if the values are being encoded correctly in the URL when passed manually.
Provide screenshots of the debug_mode output and include the full text of any errors you’re encountering. This will give us more context and help us identify the issue.
If possible, please record a detailed Loom video that includes the steps above and send it to us.
Looking forward to your response!
mibbebr,
Thank you for your interest in a mobile version of this plugin.
With each new user inquiring about it, there is a higher incentive for its development.
Print out a text element on your page with the following content: RepeatingGroup_Collab's [SB] selected_brands:each item:lowercase:formatted as JSON-safe. This will allow us to see what value is being passed into your filter.
"instagram", "samsung" are what’s inside the repeated group. The entire filter syntax being sent (without the bubble dynamics) are:
Test with hardcoded values: Try executing the workflow with hardcoded values, for example: .not("brand_name", "in", ['Instagram', 'samsung']). This will help us check if the values are being encoded correctly in the URL when passed manually.
Tried this. Same error.
Provide screenshots of the debug_mode output and include the full text of any errors you’re encountering. This will give us more context and help us identify the issue.
If possible , please record a detailed Loom video that includes the steps above and send it to us.
Sending you a video via DM, including the Supabase error log
@ZeroqodeSupport my app with your Supabase plugin doesn’t load again. Can you help me to solve? It’s very critical, since a similar thing happened a few weeks ago and lasted more than 24 hours, my users can’t not log in (custom auth used in my app). Please guys I need your help as fast as possible. Thanks.
Hello. You can tell you why it does not work out the update of data in real time?
The screenshots show that applications are different in the database and at the front in Bubble. And it is clear that there is a new line in the database, but it did not display at the front in Bubble.
In Supabase in these tables there is a ticket for Realtime on.
Thanks for reaching out and for providing the detailed screenshots.
From what we can see, your database updates are correctly applied in Supabase, but not reflected in real time on the Bubble front end. Please note that while the Supabase Pro Kit supports interacting with real-time-enabled tables, displaying changes automatically on the Bubble front end requires additional configuration.
To help us assist you better, could you please confirm the following:
Are you using the “Listen to table changes” action from the plugin in your workflow?
Is the table you’re listening to properly enabled for Realtime in Supabase (it seems so from your screenshots, but just to be sure)?
Are the changes you’re expecting related to insert/update/delete events on that table?
If everything looks good but the front end is still not updating, you might want to ensure:
That the “Listen to table changes” is set up before the data is updated.
That your Repeating Group or UI elements are configured to refresh data when changes are detected.
Let us know how it’s set up on your end and we’ll guide you through the next steps!
I used to use the “SEO” parameters of Bubble’s “current page” to point the URL to a specific object, thus transforming the “PAGE” into a “Related” page for a product or news item.
.
With the change to an external database, I realized that “Bubble” has a limitation that seems to be a “Bug” due to the following issues: “Bubble” allows RELATING groups and Reusable Elements with external databases, but the PAGE bubble does not allow access to the external database to RELATE the page to a specific product.
Bubble only allows you to link a PAGE to its own database. My question is how to link a product or news item to a specific URL.
For this URL to interact on another platform, when sharing this URL, the browser redirects the user to the specific page in Bubble.
For those of you who have encountered this question, how did you manage to link the “Correct Page” to a product with the plugin?
Based on the error ‘PGRST100 failed to parse filter (not.in.instagram,samsung) line 1 column 8,’ it seems that Supabase is expecting a different filter format. The error does not suggest any issues with formatting or encoding the values.
We recommend debugging with a simpler filter first. Try using a filter with a simple text value, such as: eq(brand_name, "Instagram")
This will help ensure that the filter works as expected. After that, you can gradually add more complex filters to check if they are applied correctly.
Let us know the results and if you need any further assistance!
yes, eq(brand_name, "Instagram") works, but this doesn’t solve what i’m trying to achieve with .not("brand_name", "in", ["instagram", "samsung"]). Could you suggest an alternative syntax or fix to achieve this?
also, curious on what exactly is causing this error?
Thank you for your patience while we continue to investigate your issue.
Just to clarify, the error code PGRST100 failed to parse filter typically indicates a problem with the choice of filter, rather than a syntax error. In the error message, “1 column 8” is actually pointing to the end of the not.in filter itself—not to the content that comes after it.
As a quick suggestion, could you please try removing the space between the parameters in your filter (e.g., use ["Instagram","Samsung"] instead of ["Instagram", "Samsung"]) and see if that resolves the error?
We appreciate your cooperation and will update you as soon as we have more information.