Hi,
The new collections are now the “Views” for tables in data&Api. Our backend is supabase with RLS enabled with policies. Now randomly we observe that if the views are kept as “authenticated” instead of public(which is a added security on top of supabase RLS) then at times the app is unable to pull those views/collections and it shows a unauthenticated error.
This was never a problem with plugins probably because then the collection was by default public.
My hunch is that maybe when a app is sitting logged in but unused, supabase expires the session after a while (few hours maybe?) and when we reopoen the app supabase checks if user is authenticated and reissues an access token and during this process(happening in milli seconds) if the weweb server sends a request to supabase to check for authentication it might get a negative response in that window, hence resulting in this error. I can’t fix both of these things since its weweb and supabase logic but with the plugins this was never the issue.
@Joyce Any fixes? What am I doing wrong?
