Skip to content

fix: invalidate stale thread participants when recipients change - #812

Merged
naveensingh merged 2 commits into
mainfrom
naveensingh/fix-wrong-recipient
Jul 9, 2026
Merged

fix: invalidate stale thread participants when recipients change#812
naveensingh merged 2 commits into
mainfrom
naveensingh/fix-wrong-recipient

Conversation

@naveensingh

@naveensingh naveensingh commented Jul 8, 2026

Copy link
Copy Markdown
Member

Type of change(s)

  • Bug fix
  • Feature / enhancement
  • Infrastructure / tooling (CI, build, deps, tests)
  • Documentation

What changed and why

  • Fix stale thread participant cache when a thread's recipient identity changes.
  • Refresh conversation participants from when opening or refreshing a thread.

Tests performed

  • I could never reproduce the original bug, but I have tested sending SMS messages to various contacts and normal app operation.

Closes the following issue(s)

Checklist

  • I read the contribution guidelines.
  • I manually tested my changes on device/emulator (if applicable).
  • I updated the "Unreleased" section in CHANGELOG.md (if applicable).
  • I have self-reviewed my pull request (no typos, formatting errors, etc.).
  • I understand every change in this pull request.

@naveensingh
naveensingh marked this pull request as ready for review July 9, 2026 01:01
@naveensingh
naveensingh merged commit 0d62201 into main Jul 9, 2026
9 checks passed
@naveensingh
naveensingh deleted the naveensingh/fix-wrong-recipient branch July 9, 2026 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

App insists on answering to wrong contact

1 participant