-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Login to second device does not have MLS capabilities #WPB-14906 #3164
fix: Login to second device does not have MLS capabilities #WPB-14906 #3164
Conversation
Bencher Report
Click to view all benchmark results
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3164 +/- ##
========================================
Coverage 54.11% 54.11%
========================================
Files 1252 1252
Lines 36519 36519
Branches 3699 3699
========================================
Hits 19761 19761
Misses 15333 15333
Partials 1425 1425
Continue to review full report in Codecov by Sentry.
|
Datadog ReportBranch report: ✅ 0 Failed, 3233 Passed, 107 Skipped, 1m 10.82s Total Time |
Quality Gate passedIssues Measures |
What's new in this PR?
Issues
When a user logs in to a second device after logging in to an MLS capable client, he does not have MLS capabilities on the second device: no previously created conversations and not MLS thumbprints in device details.
Causes (Optional)
field
creator
inConversationResponseDTOV3
suppose to be nullable.Looks like we just forgot to add "?" to the field.
So when backend sends conversations with
creator = null
parser on android side fails.Solutions
Make
creator
filed nullable. LaterConversationResponseDTOV3
mapped intoConversationResponse
which hasval creator: String?
, so it should not add any problems :)