-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-02-24] New message green line appears after a brief moment when opening the app from background #14520
Comments
@puneetlath this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@puneetlath 12 days overdue now... This issue's end is nigh! |
I think this likely needs to be Internal. |
Job added to Upwork: https://www.upwork.com/jobs/~01ecfec059338b828f |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak ( |
Hi, Eduardo from Callstack, can I take this one? |
@gedu as mentioned in Slack feel free to give this a try but there is a chance it requires backend changes, nevertheless post your findings! |
ProposalPlease re-state the problem that we are trying to solve in this issue. What is the root cause of that problem? What changes do you think we should make in order to solve the problem? greenLine-aftervisible.mp4greenLine-aftervisible-hide.mp4What alternative solutions did you explore? (Optional) |
Ah yes that is interesting. The comment says "If the app user becomes active and they have no unread actions" but then we don't actually check whether or not the chat is unread before clearing the marker. That solution sounds good to me. @eVoloshchak what do you think? |
@gedu I think this solution makes sense, thank you, I would say you can go ahead and create a PR for this. You got two approvals 🙌 |
I have read the CLA Document and I hereby sign the CLA |
@puneetlath, @gedu, @eVoloshchak Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue, PR was deployed to production 3 days ago |
Updated the title to reflect this. |
@eVoloshchak sent you a contract offer. |
Offer accepted👌 |
All done. Thanks everyone! |
@puneetlath please invite me, I'm the reporter |
@puneetlath, the PR was merged within 2 business days. I didn't review proposals, only the PR, but it looks like @gedu might be eligible for the bonus |
This is a follow-up of Expensify#14520 / Expensify#15097, where we changed the app's behavior to keep the unread indicator present after backgrounding and reopening the app.
Just gonna reopen this so we dont forget to handle the reporting bonus |
@eVoloshchak in this case, this was handled by a vendor contributor from Callstack, so the process is more similar to our Internal PR process. @hungvu193 sorry for forgetting about you! Can you apply here: https://www.upwork.com/jobs/~01ecfec059338b828f For me: https://www.upwork.com/ab/applicants/1623441417954881536/applicants |
Thank you, I've just applied! |
Paid! Should actually be done now. Thanks everyone! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Mark as read line should consistently.
Actual Result:
Mark as read line disappears then appears again.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.58-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
MZBZ5035.MP4
RPReplay_Final1674551444.MP4
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1674552168801719
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: