I need to set up Supabase + Bubble authentication via Microsoft.
Authentication is working perfectly, and Supabase is creating sessions and tokens.
However, the Supabase auth plugin is not receiving or triggering the “authentication completed successfully” event. It leaves the “is logged in” property as false, with all other data blank.
In the URL, you can see “#access_token=…”
How can I fix this?
Hi @mauricio,
Thank you for reaching out! We’re glad to hear that the Supabase authentication itself is working perfectly and successfully creating sessions and tokens.
Based on your description, the issue lies in how the URL hash fragment is being processed when Microsoft redirects back to your Bubble application.
By default, Supabase returns the session tokens (#access_token=...) inside a URL hash fragment (the portion after the # symbol). Because the browser handles hash fragments client-side, Bubble workflows and standard page-load logic often cannot read these parameters immediately. As a result, the plugin element on the page doesn’t automatically detect the incoming token, preventing the “authentication completed successfully” event from triggering and leaving the “is logged in” property as false.
To resolve this issue, please verify and implement the following logic in your application:
Initialize the Auth Element on Page Load: Ensure that the Supabase Auth element is fully loaded on the page where the user lands after the Microsoft redirect. It requires a brief moment on page load to automatically parse the hash fragment from the URL and initialize the user session.
Check the Demo Editor Configuration: We highly recommend checking out our official live demo editor to see exactly how the OAuth redirect page and workflow events are structured. You can find the links to the documentation and the underlying logic here:
Inspect the Browser Console Logs: If the event still refuses to fire, open your browser’s Developer Tools (F12) and inspect the Console tab. Look for any initialization or redirection errors coming from the Supabase script. This will tell us if a strict Content Security Policy (CSP) or an incorrect Redirect URL in your Supabase Dashboard is preventing the plugin from reading the token.
Please review the setup against the demo editor guidelines and let us know what you find in the console logs if the issue persists!
Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
Hi @mauricio,
I’m checking in to see if you had a chance to review the troubleshooting suggestions regarding your Supabase authentication setup.
Did initializing the Supabase Auth element on your landing page help capture the URL hash token and resolve the issue?
If you’ve checked your setup against our demo editor and the problem persists, please let me know what you find in your browser console logs so I can investigate further.
Best regards,
Support Team
Browse all Zeroqode Plugins for bubble