From 18c280cbb0acab18dc424b5f3a32872416501029 Mon Sep 17 00:00:00 2001 From: moojttaba Date: Wed, 3 Jun 2026 22:43:04 +0330 Subject: [PATCH] =?UTF-8?q?docs:=20activity=20log=20=E2=80=94=20backend=20?= =?UTF-8?q?v2.8.70=20(persist=20telegram=20user=20updates=20on=20sign-in)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- 09 - Audits/Activity Log.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/09 - Audits/Activity Log.md b/09 - Audits/Activity Log.md index ece6d21..77cf256 100644 --- a/09 - Audits/Activity Log.md +++ b/09 - Audits/Activity Log.md @@ -1057,4 +1057,20 @@ reviewed" handled gracefully. --- +### 2026-06-03 — backend v2.8.70 — persist telegram user updates on sign-in (new-user login) + +Investigating "new Telegram account / new device can't log in (existing works)". +telegramAuth mutates the user after the TelegramLink lookup (telegramVerified +flip, lazily backfilled referralCode, lastLoginAt) but only NEW users hit +user.save(); existing/half-created users were never re-persisted → a backfilled +referralCode never landed and subsequent sign-ins kept tripping the non-sparse +users.referralCode index. Added a best-effort user.save() before linking. +**Note:** background logs in the user's screenshots show "Backend 2.6.49" — the +deployed dev backend may be far behind (none of the 2.8.x auth/email/chat fixes +live). Asked the user to confirm/redeploy the backend and share the exact error +the new device shows (frontend surfaces backend message verbatim). +**Verification:** backend tsc clean. + +--- +