Failed to start Websocket client , error: 'Operation is not supported on this platform.'
@Tr00d is already working on this.
Since Jul 3, 2026.
Assessment
This issue has not been assessed yet.
Description
Bug report
Describe the bug
I am using Supabase v1.1.1 in a Blazor WebAssembly (WASM) application running on .NET 8. The issue occurs with this commit in the Supabase.Realtime package, so v1.1.0 is working without any issue. Specifically, the problem is on this line, where the following method is invoked:
socket.Options.SetRequestHeader(header.Key, header.Value);
This method is marked with [UnsupportedOSPlatform("browser")], and when calling InitializeAsync in a Blazor WASM application, the following exception is thrown:
Error: One or more errors occurred. (Failed to start Websocket client , error: 'Operation is not supported on this platform.')
To Reproduce
- Create a new Blazor WASM project.
- Install the Supabase NuGet package v1.1.1.
- Register Supabase in DI Container (or manually create an instance of it) as shown below:
builder.Services.AddSingleton(sp =>
{
var client = new SupabaseClient(
Constants.Supabase.Url,
Constants.Supabase.ApiKey,
new()
{
AutoRefreshToken = true,
AutoConnectRealtime = true,
SessionHandler = sp.GetRequiredService<SupabaseSessionProvider>()
});
return client;
}
);
Call InitializeAsync on the Supabase client:
await supabase.InitializeAsync();
Expected behavior
The InitializeAsync method should not throw an exception, or there should be a guard like [UnsupportedOSPlatform("browser")] to prevent setting AutoConnectRealtime to true on the WASM runtime.
System information
- OS: macOS
- Browser: Arc (Chromium)
- Supabase NuGet Package Version: 1.1.1
- Dominant language
- C#
- Stars
- 701
- Forks
- 106
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 45
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/supabase-csharp
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
supabase/supabase-csharp#440 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
supabase/supabase-csharp#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
supabase/supabase-csharp#427 ·
-
supabase/supabase-csharp#409 · 1 comment · 1 assignee ·
-
area: realtime bug parity
supabase/supabase-csharp#393 · 1 assignee ·
All issues in supabase/supabase-csharp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100