As the title states, I was prompted today to give WeWeb access to Supabase. This seemed strange since I haven’t had any issues working with my database, but I followed the platform recommendation.
Now I keep getting toast messages about errors connecting to my Supabase database. It seems after giving WeWeb access, it is pointing to a null instance. I cannot for the life of me find a way to disconnect or troubleshoot this error. I reached out to support a couple of hours ago, and wanted to see if anyone knew how to fix this issue
According to Support this issue will be fixed this week, and will not require any additional action on our side. However, I haven’t received an update for when this fix is going to be pushed live, or where to receive updates on this bug
This is actually separate. WeWeb prompted me to add Supabase on the back-end tab, in the new design. However, there is no way to disconnect on the back-end tab specifically, without undoing other work in my app. Support confirmed this was a bug, and should be fixed shortly.