Since the problem has resolved BY no one doing nothing new, I deleted all conversation but you felt the need to dig it up again and post the same thing and bashed me one more time.

The real question is "why I used a v2.13 supabase.js and got a v1 response? NOT seeking help and just curious" .

@EK You somehow had to have something mixed up. It does not come back from the server but is set in the javascript client code right before it returns to you.... v2:

return { data: { user, session }, error: null }

https://github.com/supabase/gotrue-js/blob/master/src/GoTrueClient.ts#L275

again I upgraded to v2 the day before, checked the package.json, deleted the node_module and re-install again.

Could have been cached in your browser? Not sure. But v2 code could not return without the data structure. It has been that way for months.

GoTrue was also up-to-date.

It gave me a type Error when it returned so I console.logged the whole thing to find out it was not nested in data.

Again. let us end this conversation. It was an odd case. I was not seeking help and that was the reason I did not use help.

It was just some weird stuff. By the night, the returned data was v2 and properly nested.

I'll just say for the future, make sure you understand if any of the files could be cached in your environment. This sounds like the case. But I can't prove it. I've had that happen before in different dev environments.

how can it be if I was able to open gotrue and see the v2 AuthResponse ?

anyway, have a great one

i don't recall mentioning you.

trying to use nextauth with supabase and when my email gets sent, it looks like it's trying to create a user automatically with id, name, email and image. Though it looks like it's trying to set an id with a null value? Anyone run into this? Error im getting:

https://next-auth.js.org/errors#adapter_error_createuser null value in column "id" of relation "users" violates not-null constraint {
  code: '23502',
  details: 'Failing row contains (null, null, email@gmail.com, null, 2022-12-12 05:44:22.93).',
  hint: null,
  message: 'null value in column "id" of relation "users" violates not-null constraint'
}

lol. whatever.

Hi everyone, is there a place on the dashboard where we can see the pg constraints?

heyo could someone look at my help post if they have some time? Im kinda stuck since a few weeks and would really love to get this out of the way lmao Nothing too urgent, it just annoys me that i cant seem to find my way around it haha https://discord.com/channels/839993398554656828/1051803124291088415

This is literally a help question. Also deleting messages doesn't help anyone because context is lost now. If this was posted as a thread in #1006358244786196510 then someone else hitting the same issue would be able to find it and know exactly what may have caused the issue and how to fix it.

Hi everyone is there a place on the

Hi there.

It is a help question only if I want help. I wanted post it in a bug section and could not find it.

why are you love to pile on? I wanted to end the topic a while ago.

There are no bug sections on here, there was also no bugs reported. You generally report bugs on the GitHub repo, not in a community run platform.

I DID report it as a bug and closed it as the issue resolved somehow.

Again, clearly I was using v2 and got a v1 response. I overrode the v2 AuthResponse that morning. By the night, the response was back to V2 nested in data.

Four dudes kept saying the response SHOULD be typed as AuthResponse v2. That was precisely the problem. It WAS NOT a v2 AuthResponse.

I tried multiple times to end this conversation but you all feel the needs to pile on. But at least try to explain why it happened instead of stating "it should work, it worked for me" @silentworks @Luv

Post the correct channel or it will be deleted in the future, I hope this makes it clear to you.

I deleted the converstaion after the first dude to "point out" it should be in help. What is the reason you all feel the needs to keep bringing it up. The answers I got were all the same "it should work". none of them tried to find out why it happened.

This channel's description is very clear, follow the rules or we will have to enforce them.