git » sdk » commit 8a6a4f4

Don't send fast-token with null token

author Eric Roberts
2026-09-09 14:02:14 UTC
committer Stephen Paul Weber
2026-09-09 15:05:25 UTC
parent f48a8b861475a8bf3a1653c5f5653f8e645415bd
Don't send fast-token with null token

This causes us to store the login, meaning if someone types a bad
password, we call storeLogin, and the next time they open the app
(cheogram) it shows them the chat ui and not the login screen like it
should.

This might have been done with the intent to clear the token, but the
storeLogin path doesn't work that way anyway, it would have left a
token if one was stored.
borogove/streams/XmppJsStream.hx +0 -1 
diff --git a/borogove/streams/XmppJsStream.hx b/borogove/streams/XmppJsStream.hx
index f7633f4..84665fd 100644
--- a/borogove/streams/XmppJsStream.hx
+++ b/borogove/streams/XmppJsStream.hx
@@ -287,7 +287,6 @@ class XmppJsStream extends GenericStream {
 				credentials.password = ID.unique();
 			}
 			credentials.token = null;
-			this.trigger("fast-token", { token: null });
 			return Promise.resolve(null);
 		};