-
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 RC #WPB-14906 #3165
fix: Login to second device does not have MLS capabilities RC #WPB-14906 #3165
Conversation
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release/candidate #3165 +/- ##
=====================================================
+ Coverage 54.14% 54.15% +0.01%
=====================================================
Files 1249 1249
Lines 36448 36448
Branches 3688 3688
=====================================================
+ Hits 19736 19740 +4
+ Misses 15288 15285 -3
+ Partials 1424 1423 -1
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportBranch report: ✅ 0 Failed, 3232 Passed, 107 Skipped, 1m 10.65s Total Time |
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 :)