using publishable key in local dev breaks realtime

[mash-g]

Bug report

• [X ] I confirm this is a bug with Supabase, not with my own application.
• [X ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Updating supabase cli 2.40.7 -> 2.45.5 breaks local dev realtime with the following error.

"WebSocketException: Connection to 'http://localhost:54321/realtime/v1/websocket?log_level=info&apikey=sb_publishable_&vsn=1.0.0#' was not upgraded to websocket, HTTP status code: 403"

Maybe realtime is not handling the sb_publishable key correctly? With the former version I'm using the deprecated anon key format. I "fixed" the issue by rolling back the version and can confirm realtime is working again.

I noticed the supabase_realtime_messages_publication is missing from the db in the latest version, not sure if that's intentional due to another unresolved issue: supabase/realtime#1484. Adding it manually did not fix the problem.

I'm calling: await supabase.client.realtime.setAuth(null); during setup, with RealtimeChannelConfig(private: true) on the channel.

To Reproduce

Use latter version and connect to realtime with publishable key.

Expected behavior

Realtime should connect.

Screenshots

N/A

System information

Using flutter 3.32.7, dart 3.8.1, supabase_flutter: 2.10.2, with target platform windows and building on windows.

Additional context

Add any other context about the problem here.

[sweatybridge]

Hi there, could you try the latest CLI? We fixed an issue with forwarding apikey from supabase-js to other services locally.

npx supabase@latest start

[omtodkar]

@sweatybridge studio is failing in the latest version #4222

[omtodkar]

I hope, #4221 has fix for the issue.

[mash-g]

Hi @sweatybridge, as mentioned I'm using the flutter package so the javascript package does not apply.
I tried again anyway with supabase cli 2.47.2 + supabase restart, but see the same error.
However, this time I didn't rollback supabase cli as I realised I can continue to use the anon key with the new version and realtime works as expected.

Hi @omtodkar, I did not face any issues with studio. I can access it fine in dev via the studio url from supabase status, ie http://localhost:54323.

[mash-g]

I tried to use the publishable key again with version 2.53.6, and realtime seems to be okay now.

[mash-g]

Ignore above update, seems this is still an issue.
Reverting back to anon key from publishable key fixed the issue again in dev.
Not sure why it seemed to work before.