Connect Supabase as back-end + Transfer project = Error (bug or feature?)

Ask us anything How do I?
1

Hey,

so I want to check if the behavior that I’m experiencing is bug or feature :slight_smile:
Or if I’m doing something incorrectly.
So I:

  • Created Supabase project
  • Connected it with “WeWeb Backend” new functionality
  • Added one collection (successfully fetched the data)
  • Transferred the project
  • Now I’m getting error when ww is trying to fetch the collection.

I don’t know how Supabase handles access, but if I understand correctly, if I connect with ww backend functionality, it uses OAuth to connect to my Supabase account.
So when the project is migrated to a different organization (to which I also have access) should the data source/collection reset?

After transferring the project I got an error when trying to re-setup the data collection. (see img)

image
image386×196 11.1 KB

2

Did you manage to figure this out? I have been getting the same issue on and off.

3

Nope,
I’ve decided not to use backend feature.
Instead I connected supa account with the “old” way and I’ll connect it once
a, this feature get some love wit bugfixes
b, we migrate to client’s organization