-
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: read receipts are not sent when the app is in background (WPB-8756) #3054
base: release/candidate
Are you sure you want to change the base?
fix: read receipts are not sent when the app is in background (WPB-8756) #3054
Conversation
Quality Gate passedIssues Measures |
operator fun invoke( | ||
conversationId: QualifiedID, | ||
time: Instant, | ||
shouldWaitUntilLive: Boolean = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if this is the right way to solve it, since this use case will send an encrypted message, and messages should only be sent if the app is live, to avoid breaking the session
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe the better approach is to handle it the same way we do when FCM message is received, start incremental sync and send the message when we are live then drop after ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any reason to redo the sync for nothing because the app is already up to date, all messages are synced after getting the event through FCM.
The user in this case just need to reply from notification without waiting for app to complete sync.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but user might reply from notification with some delay, and during that delay some changes (new messages) might happen. For example: user receive notification -> lose connection for 5 minutes -> some messages comes to that conversation, but there is no connection, so the client doesn't know about it -> client goes online and sends reply instantly without sync
Test Results2 314 tests - 903 2 303 ✅ - 808 24s ⏱️ - 4m 3s For more details on these failures, see this check. Results for commit 257d19b. ± Comparison against base commit 8be3015. This pull request removes 3217 and adds 2314 tests. Note that renamed tests count towards both.
This pull request removes 106 skipped tests and adds 6 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
operator fun invoke( | ||
conversationId: QualifiedID, | ||
time: Instant, | ||
shouldWaitUntilLive: Boolean = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe the better approach is to handle it the same way we do when FCM message is received, start incremental sync and send the message when we are live then drop after ?
Bencher Report
Click to view all benchmark results
|
Datadog ReportBranch report: ❌ 5 Failed (0 Known Flaky), 3072 Passed, 52 Skipped, 20s Total Time ❌ Failed Tests (5)
|
This PR is stale because it has been open 30 days with no activity. Please update it or close it in case is not relevant anymore. |
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
Read receipts are not being sent when the app is in the background.
Causes (Optional)
In
SendConfirmationUseCase
we wait until app is live to send confirmations.Solutions
Add a flag to the use case to ignore this wait if the user replies from notification.
Needs releases with:
Testing
Test Coverage (Optional)
How to Test
Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.
Notes (Optional)
Specify here any other facts that you think are important for this issue.
Attachments (Optional)
Attachments like images, videos, etc. (drag and drop in the text box)
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.