Supabase Realtime Updates Fail Only When RLS is Enabled (Despite Correct Policy/Subscription/Publication)

Hi everyone, I'm stuck on a Supabase Realtime issue where updates work perfectly fine when RLS is disabled on my campaigns table, but stop arriving at the client as soon as RLS is enabled. Setup: Next.js (App Router), @supabase/auth-helpers-nextjs, Clerk auth. Client subscribes to postgres_changes (UPDATE) on public.campaigns filtered by id=eq.${campaignId}. What I've Confirmed: Backend updates the DB correctly. Frontend subscribes successfully (SUBSCRIBED status). The SELECT RLS policy for authenticated role is PERMISSIVE and uses the correct USING expression (joining users table to compare clerk_id with (auth.uid())::text). supabase_realtime publication includes the table and UPDATE events. Client uses detectSessionInUrl: false and a stable instance (useMemo). The Weird Part: Even setting the SELECT policy to USING (true) or manually updating the row in the Supabase dashboard does not trigger the client callback when RLS is enabled. It only works when RLS is completely off for the table. It seems like RLS enablement itself is blocking the broadcast, regardless of policy logic. Has anyone seen this specific behavior? Any ideas beyond standard RLS/Publication checks? Thanks!