Supabase pro kit

[arensbpa]

Anyone have suggestions on this bug? My users can’t store data from supabase in bubble within 10 seconds of the page loading even though the realtime event subscription is almost immediate and the data fetch is on page load.

ClaimKit - 4 August 2025

UPDATE: issue is unrelated to time, it’s the first event on page load never works regardless of how much time elapses. This is one of the main issues i’ve been seeing with realtime - it says you’re subscribed to the channel but then it doesn’t work out of the gate you have to give it a kick in the ass to get it working

The inconsistencies with realtime for this plugin are insane. I don’t know how anyone uses this in a production environment.

[mina.rotari]

Hey @arensbpa ,

Thanks for the video!

Looks like the JSON response is coming in later than when the create/modify thing action is triggered. This is likely causing the issue. The real-time event fires quickly, but the data fetch takes a bit longer to complete.

Instead of relying solely on the first real-time event, you could add a conditional workflow to handle this more reliably. Here’s what I recommend:

1. Realtime Subscribe (on page load).
2. Schedule a custom event (e.g., “Verify Save”) to run 3-5 seconds later.
3. In “Verify Save”: Check if the data exists in Bubble (use a “Only when” condition); if not, fetch the data from Supabase and save it.

This should ensure the data is available and avoid relying solely on the first event.

Hope this helps.

Best,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

@mina.rotari - I implemented the verify and save worfklow, however it didn’t solve the problem even though it should… I get a very interesting bug where the “only when” condition thinks there is text saved to the field when there is not. Please see this video and you can see for yourself: ClaimKit - 6 August 2025 | Loom

I showed bubble bug team this same exact video and they said “After reviewing your setup, it appears that the dynamic value you’re using user_condition(supabase)_id is being sourced from the Supabase plugin. Since this plugin is developed by a third party, our team has limited visibility into its internal functionality and how it processes data.”

Can you please let me know why you think this is occurring? The database fetch and the realtime subscription happen on page load as you can see in the console logs on the video

[mina.rotari]

Hey @arensbpa,

Thanks for sharing the video!

It looks like the issue stems from the “Only When” condition. The debugger is showing that the ID exists in the field (because it’s being evaluated). This often happens because of timing issues , the real-time event fires before the data is fully available, causing a mismatch when the ID is checked.

Here’s how you can fix it:

1. Use the “Supabase Database Fetch” action to pull in the latest data, especially the ID. Make sure to filter by unique identifiers like user_id = Current User's ID.

2. After fetching, add a pause to give it time to fully load before the next action.

3. Instead of using the “Only When” condition in the modify action, schedule a custom event. In that event, check if:

• user_condition(supabase)_id is empty, AND
• Supabase Database Fetch’s Result: first item’s ID is not empty.Then, in the custom event, you can use “Make changes to user_component” to set the user_condition(supabase)_id to the fetched Supabase ID.

This approach checks if the ID is empty before setting the value, so it won’t try to set an ID until it’s correctly fetched. By using a custom event, we’re ensuring that the ID is only saved once the data is fully available, preventing the race condition where the data isn’t ready when the workflow runs.

Hope that helps.

Best,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

Hi @mina.rotari Mina, thanks for the response I believe i’ve implemented this the way you suggested, here is a video demonstrating the race condition still occurring somehow ClaimKit - 7 August 2025 | Loom and here are images of the setup if you’d prefer to read:

[mina.rotari]

Hi @arensbpa ,

Appreciate all the effort and the detailed info you’ve shared.

I took some time to create a test page on my side and was able to replicate the exact same output. Interestingly, the record in the DB is created with the creation date, but the actual text value is null.

I’ve gathered all the details and passed them on to our dev team for investigation. At this point, it could be related to Bubble’s async processing, but we’ll wait for the dev team’s update before making any conclusions.

I’ll make sure to keep you informed on any results we get.

Best,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

Thanks @mina.rotari, please keep me posted

[arensbpa]

While we wait on response from dev on that, can you @mina.rotari take a look at this for me? This is actually the main issue I have with the supabase plugin. What I seem to experience is even though the console shows that realtime channel is subscribed, when a realtime insert or update or event occurs, it shows up in my console but it doesn’t not actually trigger any of the realtime insert/update/event workflows that I have setup to refresh my UI. So I cannot trigger a refresh UI component event because it never fires. And so the end result is a realtime system that functions only periodically. Here’s a video illustrating this: Demonstration of Realtime Confusion | Loom

When I started using this plugin I didn’t expect to have to use those workflows to refresh the UI< I just expected the UI to refresh just like it does in bubble. So the fact that these aren’t working confounds me. I find the realtime in the plugin so unreliable that I cannot push anything to prod until I get this sorted, what am I doing wrong here? If you need more information on my setup please let me know

[arensbpa]

Any thoughts on this @mina.rotari?

[mina.rotari]

Hi @arensbpa,

Apologies for the delay and thanks a lot for walking through your setup in such detail — that’s super helpful.

Regarding the first issue: our dev team confirmed that everything works fine on their end. The key is to make sure you’re using the “DB Action Inserted” event, which confirms all incoming data before triggering anything else. We ran several tests, and the outcome was consistent every time. You can check out my test setup here:

Bubble Editor - supabase-editor

For the second issue, I’ve recorded a short video showing how to verify if update it’s triggering or not.

I hope that helps, looking forward to your feedback.

Best,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

Ok thanks @mina.rotari I’m playing with those suggestions now I’ll let you know how it goes

[arensbpa]

Ok @mina.rotari thank you for these! I have implemented the “supabase database inserted” event instead of using the “realtime inserted” event and it works well thank you!

For the second topic we are discussing, I implemented the “supabase database updated” event and then a reset a group (instead of refresh page in my circumstance) like you suggested and I get weird behavior where only the removal of information triggers the workflow which is not the case in your demo video. Please see this video: tb1.mp4 - Google Drive - 12 August 2025 | Loom

Am I doing something wrong?

[arensbpa]

@mina.rotari does what I’m trying to show in that video make sense? Do you need any other info from me?

[mina.rotari]

Hey @arensbpa,

Appreciate you sharing the extra details and the video.

I’ve just run the tests again on my end, and with a very stripped-down setup (just the “Supabase Database Updated” event triggering a reset) it behaves exactly like in the demo (event is triggering once updated). In your setup, there’s a lot more going on, so something in that chain is probably affecting when the event actually fires.

Since the plugin itself is working as expected in a minimal case, this is leaning more toward an implementation rather than a bug/issue in the plugin. Our support focuses on plugin issues/bug fixes, so we can’t really go deep into custom build troubleshooting. That said, the Bubble Forum is a solid place to get help for your exact setup, you’ll find plenty of folks who’ve tackled similar patterns.

Hope that helps clarify!

Best,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

Hi Mina, I’m trying to sync bubble and supabase auth without success. The problem is password reset - if the user is authorized in bubble and supabase and they go to change their password, bubble requires a password reset link and as far as I can see there is no update password field action for the supabase plugin so that I can update a password for a user based on their email address. You can only reset password either on bubble only or supabase only once at a time. How do you suggest doing the syncing?

[mina.rotari]

Hi @arensbpa ,

Thanks for getting back to us and explaining the situation!

From what I understand, once the user receives the password reset link via email and follows it, they’ll be redirected to the URL specified in your Supabase project settings. After they update their password on the Bubble side, they should be logged out of Supabase automatically.

At that point, the user can simply log in again with the new password, and everything should remain in sync between Bubble and Supabase.

So essentially, the sync happens through the logout/login flow after the password change.

Looking forward to your reply.

Best regards,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

Hi @mina.rotari thanks for getting back to me! I only want to send one password reset email. It would be crazy to require the user to open 2 emails (one from bubble and one from supabase). I assume we’re on the same page about that - so you’re saying to use the supabase “Send password reset request SupabaseAuth A” instead of the the bubble “Send password reset email” action and in that action you’d redirect them to your password reset page in your bubble app. This would allow me to reset their supabase password. But since the user is not logged into their bubble account, I cannot update their bubble password. So their bubble and supabase passwords are not in sync.

If I were to use just the bubble “Send password reset email” action and they were logged out of supabase, I’d have no way of syncing up the new password with a supabase account because the update user auth > new password field would only work if they were already logged into supabase.

What am I missing?

[mina.rotari]

Hi @arensbpa,

Thanks for the clarification!

Unfortunately, a full, seamless sync using just a single password reset email isn’t directly possible. This is due to how Bubble and Supabase handle authentication separately for security reasons:

• Bubble requires either the old password or its own reset flow, which sends a separate email.
• Supabase uses token-based password recovery.

You can’t bypass this without custom hacks, which could compromise security or create a poor UX.

One potential workaround would be:

1. After the user resets their password in Supabase, trigger a backend workflow in Bubble.
2. Send a custom “sync link” via email to the user.
3. When they click it, it triggers a Bubble password reset to match the Supabase password.

This still involves multiple steps/emails, but it allows you to keep the account in sync safely.

Best regards,
Support Team
Browse all Zeroqode Plugins for bubble

[arensbpa]

Ok and so when you send the sync link email via a backend workflow are you suggesting you would include the password in a url parameter? How would you actually pass the new supabase password to that bubble reset password action?

[mina.rotari]

Hi @arensbpa,

Thanks again for your patience and for sharing that detailed reference.

We took a closer look at the feature you mentioned from the other Supabase plugin, and while it’s a useful approach, it’s unfortunately not something we can implement on our side at the moment.

For now, the best workaround we can suggest is to create a backend workflow that updates the password by calling the API endpoint right after the password is changed in Supabase.

We’ll keep your suggestion noted for future consideration though, it’s definitely something that could improve the integration long term.

Best regards,
Support Team
Browse all Zeroqode Plugins for bubble