Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

` let { data: users, error } = await supabase.from("users").select("user_id, cash").eq("user_id", userID);`

Try console.logging the payload inside the callback function. Nothing looks wrong to me. Try looking at the network tab in devtools to see if a websocket connection was created. Also try actually rendering the post variable. I think you're just forgetting to mutate the posts variable when a payload comes in, so you're probably looking for something like `setPosts([...posts, payload.new])` **made an update, something was wrong

I did that too
There is a socket created, but I'm monitoring the response and it's always blank

don't bother with another effect that reacts to post. just call setPosts in the `.on((payload) => {}) `function

can you screenshot the supabase dashboard?

man what a dumb mistake
I just saw everything was enabled, I thought it was ready

yeah they can make it a bit more obvious 🙂

No error, it shows null, and the data array is empty too

If I query anything without the filters it works

user_id is a text value and the variable I'm passing to eq is a string, if that makes a difference

I've been at it all morning, can't figure out what's wrong.

I am getting the error; "Error: supabaseUrl is required."

When console logging it shows the actual url thought (Keys are inside '.env.local'

```
import { createClient } from "@supabase/supabase-js"

const supabaseUrl = process.env.supabaseUrl
const supabaseAnonKey = process.env.supabaseapi

console.log(supabaseUrl)

const supabase = createClient(supabaseUrl, supabaseAnonKey)

export { supabase }
```

Hi everyone! I'm having an issue with token refresh in NextJS. Once the token expires,  I can't access protected routes because `user` is `null`. 

Has anyone else encountered this as well?

It seems that I can't use `{ count: 'exact' }` with `rpc`. Not sure if it's because I'm providing params to my stored procedure function. Has anyone else encountered this problem? I'm thinking about creating an issue on https://github.com/supabase/postgrest-js and just wanted to check here first. Maybe I just don't have the `count` at the right place.

For example: 

```
let query = supabase
query = query.rpc(
  'custom_filter',
  { filter_params },
  { count: 'exact' },
)
const{ count, data, error } = await query.range(0, 99)
```

In the meantime, it seems that I can get by with the following workaround before sending the query. The `{ count: 'exact' }` also works fine in `select`.

```
query.headers = {
  ...query.headers,
  Prefer: 'count=exact',
}
```

<@779770020372021319> I highly doubt that count should work with rpc. But then when you said you have a functioning work around, I was confused too. Are you sure that it's working?