A React Native library for connecting to SignalR servers with WebSocket support and automatic reconnection.
react-native-signalr is a library that enables React Native applications to establish and maintain real-time connections with SignalR servers. It provides a seamless integration for bidirectional communication between mobile apps and backend services using SignalR's hub-based architecture, handling WebSocket connections, automatic reconnection, and fallback transport methods.
React Native developers building mobile applications that require real-time, bidirectional communication with backend services using the SignalR framework, particularly those integrating with existing .NET or ASP.NET Core SignalR hubs.
Developers choose react-native-signalr because it offers a lightweight, reliable bridge specifically designed for React Native, with built-in error handling, automatic reconnection, and long polling fallback without pulling in the entire jQuery library—only shimming the few methods SignalR needs.
Use SignalR with React Native
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Only shims the few jQuery methods SignalR needs, avoiding the overhead of the full library, as noted in the README's emphasis on not pulling in entire jQuery.
Handles automatic reconnection and fallback to long polling when WebSockets fail, ensuring reliable real-time communication in React Native apps.
Provides detailed error messages and connection state monitoring, with examples in the README showing how to catch and debug SSL and network issues.
Tested on iOS and Android with no known issues, making it suitable for building mobile apps that need consistent SignalR integration.
Relies on jQuery shims, which the README acknowledges as an ongoing task to remove, indicating potential breaking changes or maintenance overhead in the future.
Requires manual App Transport Security adjustments for HTTP connections on iOS, as highlighted in the error handling example, adding setup complexity.
The README is brief with only one example and minimal API details, which can hinder advanced usage or troubleshooting without digging into source code.