Can't create INSERT policy

Bug report

Describe the bug

I am unable to create new INSERT policies. It complains of a missing definition even though it’s set.

To Reproduce

1. Create a new insert policy
2. Enter a definition
3. Click save

Expected behavior

Policy should be created, instead we get an error asking for a definition or a check.

Screenshots

System information

Firefox 89 Windows 10

Additional context

Without going to “Advanced” for INSERT, you can’t actually set a definition (“with check” is the only thing that shows). Related?

[easy-street]

I also wasn’t able to do an INSERT despite the policy:

await supabase.from("mailing_list").insert({
  email: email.trim(),
})

Getting back

{"hint":null,"details":null,"code":"42501","message":"new row violates row-level security policy for table \"mailing_list\""}

@alexturpin there is a note in the insert docs that describes this issue:

By default, every time you run insert(), the client library will make a select to return the full record. This is convenient, but it can also cause problems if your Policies are not configured to allow the select operation. If you are using Row Level Security and you are encountering problems, try setting the returning param to minimal.

So, two options:

• add a policy allowing SELECT
• set the returning param to minimal:

await supabase.from("mailing_list").insert(
  {
    email: email.trim(),
  },
  { returning: "minimal" }
)

[jstansbe]

I also glossed over this and wasted a bunch of time spinning my wheels… thank goodness I found this issue. I hope more attention can be brought to this “gotcha” detail so others don’t go down the same path. Maybe add a warning on the policies section (auth/policies page) that a table only has an insert setup and could cause insert op to fail (code 42501) until select access is setup.