fix(webapp): Implement recovery mechanism for epoch number mismatch between CC and local state [WPB-23452]#20515
Merged
thisisamir98 merged 1 commit intodevfrom Feb 26, 2026
Merged
Conversation
…etween CC and local state [WPB-23452]
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #20515 +/- ##
==========================================
- Coverage 45.38% 45.36% -0.02%
==========================================
Files 1636 1636
Lines 40343 40344 +1
Branches 8330 8330
==========================================
- Hits 18310 18304 -6
- Misses 20099 20104 +5
- Partials 1934 1936 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Contributor
|
🔗 Download Full Report Artifact 🧪 Playwright Test Summary
specs/CriticalFlow/oneOnOneCall-TC-8754.spec.ts (❌ 0 failed,
|
screendriver
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
if we read the epoch number from core crypto in case welcome is processed sooner than reset conversation will exists on core crypto but epoch number will be 0, on this scenario user will have a local unestablished MLS conversation that does exists on core crypto but with epoch number of 0. the recover for this scenario had the issue of reading the epoch number from backend (latest epoch number) hence app was trying to send MLS messages while the conversation was not established on core crypto level.
Closing #20508 with this.