Hey guys, I'm trying to upload an avatar for authenticated users, but I keep getting this error:

error: "Key is not present in table \"users\"."
message: "insert or update on table \"objects\" violates foreign key constraint \"objects_owner_fkey\""
statusCode: "23503"

I'm not sure of what it means 🤷‍♂️ Maybe my policies are not properly set? Or could it be that the

roles=authenticated

property of the request is not understood by supabase? Any advice about this?

Hello @Manuel Coffin! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

How are you doing the upload? The error is that you have an owner value that is not null, or a UUID in the auth users table. I assume that value is set to auth.uid() by the storage upload process, but have not looked at the code.

manuelcoffin (2022-03-22)

I'm calling the function like this:

js
const fileExt = values.avatar[0].path.split(".").pop()
            const fileName = `teacher_${profile.id}.${fileExt}`

            let { error: uploadError } = await supabase.storage
              .from("public")
              .upload(`${"avatar"}/${fileName}`, values.avatar[0])

Where

values.avatar[0]

is of type

File

Manuel isn't the only one with this issue. 2 more people got this issue, and it looks like they didn't be able to solve it

I'm not sure about what you are calling an owner value? Isn't the request to supabase accompanied by a auth token?

Yes on jwt token, that is why I was asking how you were calling it...

What I find a bit weird is that I used the same code to upload images the other day, and I got it to work, the only difference is that I wasn't using Supabase auth then

2 things to try: - Can you logout and signin again with Supabase's api? - Check logs in Settings > logs > API/Database?

Ok I'm going to check that, thanks!

The error has nothing to do with policies, that I can think of at least. @User are those other situations in discord? I don't find any in quick search of github.

Yes there is, 2 more: https://discord.com/channels/839993398554656828/843999948717555735/929782874176114718 https://discord.com/channels/839993398554656828/843999948717555735/930761550137028668

I am able to logout and login again with the supabase api. I can also see the logs, I'm not sure how to interpret the request: POST | 409 | 52.59.247.62 | 6eff9e248a4091e4 | http://[MY_SUPABASE_ID].supabase.co/rest/v1/objects?columns=%22name%22%2C%22owner%22%2C%22bucket_id%22 | node-fetch/1.0 (+https://github.com/bitinn/node-fetch)

409 means there is a conflict

So one of the other cases mentions creating a users table....

Humm, I had an user table at the beginning, and it worked, but I removed it because I thought it was redundant with the authentication table of supabase ...

it could make sense with the 409 status if for some reasons ``users`` is the same of ``user``, and ``user`` is needed

actually the original error I got in the frontend is

error: "Key is not present in table \"users\"."

like postgres takes the ``user`` name and automatically add the ``s`` at the end because of plural (i already got this issue in another project so)

it seem indeed related to the user table

yeah, but why

yeah I don't get it either, I thought supabase Authentication could work on its own

Let's create an issue on the Github, there is 2 more people getting the error, could be good to report it

Ok, I'm going to try to reproduce it on an empty project

CONSTRAINT "objects_owner_fkey" FOREIGN KEY ("owner") REFERENCES "auth"."users"("id") The fkey seems OK, so not that simple.

ah

Let's create an issue with a reproduction (if you can) and drop the link here. If someone else has the issue, they gonna be able to have a discuss about it. I'm gonna continue to search what could be the problem, and drop the answer in the issue if found

Deleted sorry

I keep investigating, now that I added again the Users table, I got a different error:

error: "invalid signature"
message: "invalid signature"
statusCode: "400"

Since I'm on a BlitJs project, that has a default session management, I wonder if there could be some interference between the supabase session and the blitzJs session. But I have checked, the authorization token sent in the headers in the same that I get when I call

supabase.auth.session()

Just dropping this here... storage does its own decoding of the jwt to get sub(owner id). Which it puts in the owner column before calling postgres (with the original jwt header) to do the insert. RLS would be done on the original header... Nothing wrong with that, but it is different code than auth.uid() with PostgRest doing the decoding.

Ok, so I figured the problem I think. I had the auth cookies set multiple times, which caused the invalid signature error. So I removed all my cookies related to supabase and blitz, and now it works! I still need to work on my row level policies now, but it seems to be all good. Thank you guys for your help! No need to open an issue 🙂