From 1336194cf4bbea05516fb03d2821c409ac97e014 Mon Sep 17 00:00:00 2001
From: Joshua Goins <josh@redstrate.com>
Date: Sun, 9 Nov 2025 10:07:59 -0500
Subject: [PATCH] Don't send an erroneous SetTypingJob on start-up

You can see this while starting NeoChat, as it always fails because
localMember() isn't valid at this point. This is called during the
ChatBar setup as we're setting up the text, which also happens during
room switch.
---
 src/libneochat/neochatroom.cpp | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/libneochat/neochatroom.cpp b/src/libneochat/neochatroom.cpp
index 1c83857a4..ee11c78e3 100644
--- a/src/libneochat/neochatroom.cpp
+++ b/src/libneochat/neochatroom.cpp
@@ -346,6 +346,10 @@ void NeoChatRoom::forget()
 
 void NeoChatRoom::sendTypingNotification(bool isTyping)
 {
+    // During the chatbar setup sequence, this may get called while we're still initializing
+    if (localMember().isEmpty()) {
+        return;
+    }
     connection()->callApi<SetTypingJob>(BackgroundRequest, localMember().id(), id(), isTyping, 10000);
 }