Hey did you figure this out? I’m having the same issues
hi @ZeroqodeSupport - thanks for your patience. Just tried it without a space in between and it’s still the same error: PGRST100 failed to parse filter
EDIT. BELOW IS SOLVED!
also, i have one more question that i hope you can help me with. i’m having issue with the Storage RLS error currently.
I set my INSERT RLS to only
(auth.role() = ‘authenticated’::text)
but even with that lax of authentication, i’m still getting a 403 error response:
statusCode: ‘403’, error: ‘Unauthorized’, message: ‘new row violates row-level security policy’
Similar RLS on other tables doesn’t generate the same error as it is for Storage
This is what I found as similar issue via the supabase github:
Bug: Storage Upload RLS Check Fails with Contradictory 400/403 Response · Issue #35157 · supabase/supabase
Hello,
@arensbpa
Thank you for reaching out!
Have you tried the solutions mentioned in this post?
If not, please try implementing them in your app and let us know if the issue is resolved.
@steven.h.liu.1 After researching your issue in detail, I came across this discussion, which mentions a similar problem. The solution that worked for others was to enclose the values in parentheses and remove any spaces, like this:
.not("brand_name", "in", "(instagram,samsung)")
Please let me know if this solution worked for you!
Best regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
1 Like
Hi ! Im really interesting par supabase and bubble.
But before buying the plugin I would like to get the answers to these questions:
Is the plugin compatible with bubble web app or only on mobile app?
I would like to use supabase only to manage authentication. The rest of my data would be on another service. Is this use case ok?
Thanks !
Hey @m.voyen ,
Thank you for contacting us.
You can use Supabase just for authentication and handle the rest of your data with another service. The Supabase Pro Kit plugin by Zeroqode supports this — it lets you manage user sign-up, login, logout, and session handling. Once authenticated, you can use the returned token to connect your users with your other backend or database.
As for compatibility, our developers are actively working on making the plugin fully compatible with Bubble web apps. As soon as this feature is released, I’ll make sure to let you know!
Have a nice day!
Best Regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
1 Like
Thank you for your quick reply !
I will wait few weeks/month before to start
Hello,
@arensbpa, is your inquiry still relevant? Were you able to apply any of our suggestions?
@steven.h.liu.1, did the solution help resolve your issue? Please let us know if you managed to apply it successfully.
Looking forward to your response!
Best Regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
Hey @arensbpa ,
Thanks for your message. 
Let’s keep the discussion in a single thread so it’s easier to track and avoid any context being lost. Main thread here
Best,
Support Team
Browse all Zeroqode Plugins for Bubble
hi @ZeroqodeSupport- apology, my job had a busy few weeks.
I just tested it with hard code and it works!
so i assume if i were to turn this into the bubble dynamic links, it would look something like this:
.not("brand_name", "in", “(RepeatingGroup_Collab's [SB] selected_brands:each item:lowercase:formatted as JSON-safe)”)
Hi steven.h.liu.1!
First of all—no need to apologize at all! Life gets busy, and we completely understand. 
We’re just glad to hear back from you—and even more excited that the hardcoded solution worked on your end!
Regarding the dynamic expression you’ve shared:
RepeatingGroup_Collab's [SB] selected_brands:each item:lowercase:formatted as JSON-safe
That’s a solid start, but we wanted to point out one potential issue—each item:lowercase:formatted as JSON-safe tends to preserve the array-like format, including quotes and spacing, like this:
["instagram", "samsung"]
To make it work as expected, you’ll likely need to manipulate the values a bit further—specifically by joining them using the :join with operator (e.g. :join with ",") instead of formatting them as JSON. This will give you a clean, comma-separated string like:
instagram,samsung
To help illustrate this, we’ve set up a quick test page you can review and replicate:
Live Page: https://egorsmorodinov-66234.bubbleapps.io/version-test/test
Editor View: Egorsmorodinov-66234 | Bubble Editor
Please take a look and let us know if this approach solves the issue for you—we’re happy to assist further if needed!
Best regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
Hi @ZeroqodeSupport- ty. let me take a look and give it a try.
In the meantime, I do have a more basic question.
To achieve persistent auth across multiple pages, I would place the “Supabase Auth” plug-in on each of the pages. However, I was placing the “Supabase Auth” across all elements (e.g., pages, repeating elements, pop-up, etc.). I think that is disrupting the auth session and sometimes it would show me as I’m logged out (not sure if that’s the true cause).
Do you have recommendations on where to place the “supabase auth” elements to ensure a continuous session across the entire site? How about the reusable popup (e.g., a sign-up page popup)?
This is a screenshot of my current bubble page schema (still need some clean-ups):
Hi steven.h.liu.1,
Thanks for your question. For persistent authentication across multiple pages, we recommend first reviewing our guides here:
In general:
- Set the Supabase Auth element at the page level, not inside repeating groups, popups, or other conditionally loaded elements. This ensures it’s initialized once when the page loads and avoids session interruptions.
- Use only one instance of the element per page to prevent re-initializing the session and potentially logging the user out.
Let us know if you have more questions!
Best regards,
Zereqode Support Team
Browse all Zeroqode Plugins for Bubble