Skip to content

fix(chat): derive call-started banner from live events, not loaded history - #6505

Closed
mahibi wants to merge 1 commit into
masterfrom
bugfix/noid/fixCallStartedInfoWhenNoCall
Closed

fix(chat): derive call-started banner from live events, not loaded history#6505
mahibi wants to merge 1 commit into
masterfrom
bugfix/noid/fixCallStartedInfoWhenNoCall

Conversation

@mahibi

@mahibi mahibi commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

.. wont be merged as it's too complicated. It was just a try to derive call started messages reliably without room requests while fixing the current bugs it has.

Will be replaced by the simpler solution #6503

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not needed
  • 🔖 Capability is checked or not needed
  • 🔙 Backport requests are created or not needed: /backport to stable-xx.x
  • 📅 Milestone is set
  • 🌸 PR title is meaningful (if it should be in the changelog: is it meaningful to users?)

🤖 AI (if applicable)

  • The content of this PR was partly or fully generated using AI

…story

The call-started/ended banner was reconstructed by re-scanning whatever
message window happened to be loaded (chat tail, an anchor/context jump,
or a paginated history block). Since window contents don't correspond to
"what actually just happened," this made the banner reappear for calls
that had long since ended whenever an unrelated history load surfaced an
old, dangling call_started.

Replace that with an event stream: ChatMessageSyncer now reports a call
system message via Events.onCallSystemMessage only when the containing
batch is confirmed to reflect the conversation's true current tail —
excluding bounded historical fetches (jump-to-message, backlog rounds
that haven't caught up yet) and picking the chronologically last
decisive message by id rather than trusting array order, since an
unconditional "newest messages" fetch returns newest-first. ChatViewModel
seeds the banner once from the initial tail load for instant display on
open, then updates exclusively from the new callSystemMessageFlow.

Assisted-by: Claude Sonnet 5 <noreply@anthropic.com>

Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
@mahibi mahibi self-assigned this Aug 17, 2026
@mahibi mahibi closed this Aug 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

APK file: https://github.com/nextcloud/talk-android/actions/runs/32054891916/artifacts/9296249763
To test this change/fix you can simply download above APK file and install and test it in parallel to your existing Nextcloud app.
qrcode (please click on link to get QR code displayed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant