Task table fails to receive any SUPABASE realtime events when the app is launched from a cold start
5 Replies
I've seen some odd cases recently where the user session does not seem to be getting into realtime. Try going back to before 2.54 supabase-js if you have control over that.
Otherwise add realtime.setAuth(user.session.access_token). Pass the access_token from the session.
The other test would be to turn off RLS on the table and see if it works.
This is the call I'm talking about. It is supposed to be only needed for custom tokens, but I've seen 3 cases here in the past week of it being needed. https://supabase.com/docs/guides/realtime/postgres-changes#custom-tokens
Nothing back from Supabase yet confirming an issue.
https://discord.com/channels/839993398554656828/1414876335662301194
@garyaustin I love you.
Adding realtime.setAuth(user.session.access_token) fixed it.
ur a g
I'll add this to my notice to SB devs there is an issue.
Are you using SSR?
Appericate you 🙏
No I am not using SSR
I'll explain the issue I was having fully when I get home if you want.
Just wanted to know if SSR was pulling in the >= 2.54 supabase-js where the problem seems to have started.