Catch (and retry?) websocket errors

[szechyjs]

Which packages are you using?

stream_chat_flutter, stream_chat

On what platforms did you experience the issue?

iOS

What version are you using?

9.13.0

What happened?

I got some crash reports with the following. This is obviously caused by some mobile connection issue, however I would think that the client would handle this websocket error better like it does the api requests.

WebSocketChannelException: SocketException: Failed host lookup: 'chat.stream-io-api.com' (OS Error: nodename nor servname provided, or not known, errno = 8)

Steps to reproduce

Unknown

Supporting info to reproduce

I noticed that the default RetryPolicy for StreamChatClient always retries for StreamChatNetworkError however websockets don't seem to be included in this, should it?

Relevant log output

Flutter analyze output

Flutter doctor output

Code of Conduct

• I agree to follow this project's Code of Conduct

[xsahil03x]

Hey @szechyjs , we automatically starts reconnection when the websocket disconnects. The only place we actually throw these exceptions are in the connectUser call, which makes sense for the api.

Also, can you share some extra information and stacktrace of this exact exception so that we can check where exactly it's coming from?

[szechyjs]

Unfortunately Crashlytics isn't giving me a full stack trace on these because its coming from an async callback.

[xsahil03x]

Hey @szechyjs , can you show me your crashlytics setup? Are you using logHandlerFunction in order to log crashes?

[github-actions]

Hey, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[szechyjs]

  // Initialize Firebase Crashlytics
  if (!kDebugMode) {
    FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalError;
    PlatformDispatcher.instance.onError = (error, stack) {
      FirebaseCrashlytics.instance.recordError(error, stack, fatal: true);
      return true;
    };
  }

[szechyjs]

I just added the logHandlerFunction as mentioned above, hopefully this provides more insight into the issue.

void chatCrashLogger(sc.LogRecord record) {
  FirebaseCrashlytics.instance.log(record.message);
}

sc.StreamChatClient buildStreamChatClient(String apiKey) {
  return sc.StreamChatClient(
    apiKey,
    logLevel: kDebugMode ? sc.Level.WARNING : sc.Level.SEVERE,
    logHandlerFunction:
        kDebugMode ? sc.StreamChatClient.defaultLogHandler : chatCrashLogger,
  )..chatPersistenceClient = chatPersistenceClient;
}

[xsahil03x]

Hey @szechyjs , Is this crash reported on debug builds or release one? I am suspecting that it's not actually a unhandled exception but a log we report in the websocket.