Not familiar with this issue, connected with Websocket/Realtime in databases

TypeScript

 @override
  Stream<SubscribeRealtime<User>> streamUsers({required Realtime realtime}) {
    _logger.info('Subscribing to user stream');
    final subscription = realtime.subscribe(
      [
        // ignore: lines_longer_than_80_chars
        'databases.${userCredential.databaseId}.collections.${userCredential.collectionId}.documents',
      ],
    );

    return subscription.stream.map((event) {
      return SubscribeRealtime(
        data: User.fromJson(
          event.payload,
        ),
        type: SubscribeRealtimeType.fromString(
          event.events.first,
        ),
      );
    });
  }

TL;DR

Developers are experiencing an issue with Websocket/Realtime in databases that is new and was not occurring before. The provided code snippet shows how they are handling subscription to user streams. Solution: The error could potentially be related to the way the subscription to the realtime data is being handled in the code snippet. Double-check the implementation and ensure it aligns with the requirements for Websocket/Realtime in databases.