publishable key is set.
after trying to display a simple test-table from supabase within the table editor the error-code says “supabasekey” ist required. a refresh gives an “unable to load data for table”. have used perplexity for hours to fix bug. Not an RLS issue in Supabase, table is exposed, policy is set…How solve?
Hey @daniel121068 
Would you mind sharing a short video walking us through how things are setup in WeWeb and Supabase? It’s a bit difficult to help without that.
Feel free to reach out to the private support chat directly if there’s anything that’s not safe to share in public.
Hey @jefeOliveira
There are 2 different issues:
Users sometimes got a 403. This bug fix has been pushed to production. If you get a 403, please contact support immediately and let them know it just happened.
Users sometimes see a 500 error (like in your screenshot). We are currently looking into this but don’t have an ETA for the fix. In the meantime, you can usually solve it by recreating the table or reconnecting your Supabase account.
Yep support did a great job going through the fixing process, it is fixed now, thanks team! you guys rock 
quick question, this new supabase integration (weweb as a middleman) requires Launch+ plan or Front-end only does the job? does is uses weweb`s Bandwidth and Compute?
If you want to use WeWeb as the “middleman”, it does require a WW Cloud plan with backend - so Launch+ as minimum.
My supabase plugins, both auth and datasource, has stopped working last night.
I’ve tried adding the keys again, both public and service role keys, but the configuration screen hang and doesnt let me go further.
Don’t know if anyone else is down because of this. I’ve sent a support request 3 hours ago, and recieved no answer so far.
Hey @thomlov
I see support answered you. Don’t hesitate to follow up with the team if anything is still unclear.
