Skip to content
pubscout

signalr_netcore

1.4.4, released a year ago by an unverified publisher

Flutter client for ASP.NET Core SignalR supporting WebSocket, SSE, LongPolling and MessagePack.

Quiet but busy
$ flutter pub add signalr_netcore
Source repository

What it does

Provides a SignalR client that can invoke hub methods and receive server callbacks. Supports automatic reconnect, multiple transport protocols and optional MessagePack serialization.

AI-written summary of version 1.4.4, based on the package's README and metadata. Report an inaccuracy

Use it when

  • Real‑time communication with an ASP.NET Core SignalR server
  • Need client‑side streaming or auto‑reconnect
  • Cross‑platform apps (mobile, desktop, web) requiring SignalR

Skip it when

  • Only simple REST/HTTP calls are needed
  • Targeting platforms where SignalR headers aren’t supported without work‑arounds

Strengths

  • Multiple transports (WebSocket, SSE, LongPolling)
  • Automatic reconnect and streaming support
  • MessagePack protocol for efficient payloads
  • Works on Android, iOS, Windows, macOS, Linux, and Web

Weaknesses

  • Limited to ASP.NET Core SignalR servers
  • Web platform header handling can be tricky
  • Documentation focuses on basic usage, advanced scenarios sparse

Setup

Kind
Flutter widgets
Effort
Medium
Code generation
No
Direct dependencies
6

Add the package, import signalr_client, configure HubConnectionBuilder with URL and optional HttpConnectionOptions (e.g., logging, token).

import 'package:signalr_netcore/signalr_client.dart';

final hubConnection = HubConnectionBuilder()
    .withUrl('https://example.com/hub')
    .configureLogging(Logger('SignalR'))
    .build();
await hubConnection.start();
hubConnection.on('receiveMessage', (args) => print(args));

Alternatives

Packages that do the same job and could replace signalr_netcore.

Works with

Packages commonly used together with signalr_netcore: ones it builds on, ones built on it, and its own family.