Closed mrigo closed 9 months ago
Hi, I see nothing wrong with your code. But it seems very close to the code from our demo app, which does not have this issue AFAIK. Did you try with the demo app? Do you reproduce the issue there?
Same issue in my case. I tried also with demo app code.
@davidpelissier Not sure I understand, did you try the demo app hooked up to your (remote) supabase instance, or with the provided local supabase instance? If you are using the local instance, did you change anything in the code or in the supabase settings? Can you provide more info to help us reproduce and debug the issue, like e.g. network traces? Thanks
@mrigo have you found any solution? I have the same error in next js. It is not adding 'apikey' to the request headers
I apologise for the poor file structure but the apiKey is not being included in the headers of the request
Nott sure if I read the code correctly but it seems that the apiKey is set only when there's an autheticated supabase session
dataProvider.ts
Indeed, we should always pass the provided key. Thanks for the report!
I have the same error which is problematic.
Hi, I can't connect to supabase because the api key isn't passed in the request headers.
I've logged the anon key and is correctly passed. I've checked the network request, using plain supabase-js the apikey is passed, but with the dataprovider the apikey isn't in the request.
Thanks