_k1ngarthur

does your status show everything is healthy?

How did the branch get a Nano compute if the main is on micro? I think branches should follow the main project

i noticed here that they just had ```export default defineNuxtConfig({ modules: ['@nuxtjs/supabase'], }) ```

https://supabase.nuxtjs.org/getting-started/introduction

But i would still use support as it is such an important table i wouldn't risk doing it myself personally lest i miss something important

Here is what the table definition looks like

This is a whole other issue as there should be an auth.users table. I think you will have to reach out to support to resolve this since recreating that table might be quite difficult without support help

you can go into the edge function details to check if that is the issue

Usually these 401 errors would occur if you are setting `verify_jwt` on despite using the new JWT signing keys https://supabase.com/docs/guides/functions/auth

Namely:

There is this guide that might help https://supabase.com/docs/guides/troubleshooting/migrating-auth-users-between-projects

For edge functions, all you have to do is make sure is download the edge function using the cli `supabase functions download`. I think you have to do that per functions but maybe you can combine with `supabase functions list` to create a short script. Migrating the `auth.users` is a bit more challenging i think, if this is your actual database in production then you shouldn't be migrating users down most likely. If it is some user test data, perhaps you would be better off recreating it?

see if modifying that fixes things, otherwise if you could share the SQL code that would help

This might be an SQL error, i found this recent message which might be helpful https://discord.com/channels/839993398554656828/1220399186399461386/1220401580826820701. From what i can tell they were using double qoutes around "auth.users" instead of auth.users

I think best thing to do is file an issue on github or comment under an existing one

yep

No worries, and yes that is the same result i was seeing when i searched. This is part of PostgreSQL and not Supabase

I can imagine that there is stuff in the config.toml like `# JWT issuer URL. If not set, defaults to the local API URL (http://127.0.0.1:<port>/auth/v1).` where if you don't change it, thinks get into a broken state

Try `supabase stop --no-backup` and then do `supabase start` if this is still an issue, you probably need a full wipe to get this working again. If you click on the user details does anything strange come up

Debit card payments should work, this is what i have used historically

Even then that would suggest the issue is with the email content most likely

Unless the issue is specifically because you are using edge functions and not using edge functions everything works?

Resend has a section on deliveraibility insights here https://resend.com/docs/dashboard/emails/deliverability-insights and also a few other pages. Usually these things are either 1) A problem with your sending address or how you're sending emails or 2) A problem with the content of the email. I would double check that both are meeting best practises.

Yeah give it a day or two and if you haven't got back then we can raise the ticket in an informal queue. All this does is check that your ticket made it to the infra queue

When did you get this ticket id?

This is a community server so i'm afraid if you have already reached out to support, there is not much more we can do.

if you don't see any of this try updating your visual studio code, i realised that was what was causing some issues on my side

the one that looks like a fork and spoon

after you ad the vscode config to `.vscode/mcp.json` you should be able to click this button here

So i managed to get this working after a while using this guide here https://supabase.com/docs/guides/getting-started/mcp

Slightly unclear about the flow that is happening here, user clicks reset password -> an email is sent with a confirmation url -> email leads user back to the app -> you exchange any token? What flow is going to the link initiating and where do app links come into this. If you any code snippets of screenshots that might help, please share

Thanks for sharing!

no problem

I'm sure there are more but i guess this is how the kotlin library filters stuff

I think they are just different way of expressing matching `FilterOperator.IS` is value a = value b, `FilterOperator.IN` is value a within the set of (a, b, c) etc

check if `_text` exists in other PostgresTables also, i doubt that there are any modifications being made on top of Supabase like this

Do read replicas get a seperate project ref?

``` supabase --experimental \ --project-ref <project-ref> \ postgres-config update --config shared_buffers=250MB ``` you can only modify the shared buffers at the project level

Judging by this https://supabase.com/docs/guides/database/custom-postgres-config

You could try restarting to instance to see if that resolves the issue

What region are you/your project in. Could it be affected by https://status.supabase.com/

Double check that the steps you followed in the video line up with this https://supabase.com/docs/guides/auth/social-login/auth-google doc

https://stackoverflow.com/questions/70638732/error-message-you-cant-sign-in-to-this-app-because-it-doesnt-comply-with-goog here could be one source of the error

So you have access to 1) Supabase dashboard and 2) google console?

It says here that you connect manually to Supabase via rork

What guide have you been following to set up google auth?

What is the issue? Logs/screenshots would help

I think seperate supabase projects makes more sense whenever auth has to be seperate. What does the shared projects even mean here if users are uploading on different sites? What is the real world model here

https://discord.com/channels/839993398554656828/1346379949979992147/1346424639060049973 and https://discord.com/channels/839993398554656828/1404939072740528139/1404942446043070474 are some other threads with similar issues to yours in case the connection being used is not the root issue

Are you using the transaction pooler or the session pooler?