-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-04-13] [$4000] Switching other app after receiving messages, message will be marked 'read' (I.e. message sender's name not bolded) #15634
Comments
Triggered auto assignment to @bfitzexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Removed the reference to '3/4' users in the title since I was able to reproduce with just a single new message coming in. |
Job added to Upwork: https://www.upwork.com/jobs/~012f05dfc9d55964fa |
Current assignee @bfitzexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Triggered auto assignment to @Beamanator ( |
@bfitzexpensify Should this issue be put on this tracker too? |
Is this bounty still available? |
This comment was marked as outdated.
This comment was marked as outdated.
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@bfitzexpensify @bernhardoj Is it possible to get access to this link? https://stackoverflow.com/c/expensify/questions/13283/13284#13284 I will need to follow the steps for the Android build, however, it seems like I need expensify.com email account to access it |
I believe that's internal only. You can follow the steps here instead. |
Thanks for the help here @bernhardoj. @nirodg As @bernhardoj mentioned you can use the steps to create the Android build, but I believe running the dev build with USB debugging on the physical device should be enough here. |
Your Expensify account email: kartikyadav637@gmail.com |
This comment was marked as outdated.
This comment was marked as outdated.
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.95-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-04-13. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@Beamanator @bfitzexpensify I think the Test steps in the PR should be enough for the regression test proposal. I think we should add a regression test because I checked the PR and I couldn't pinpoint to the exact reason as to this stopped working or whether it ever worked before we added Freeze. Lastly, @bfitzexpensify I think this is ready for payout. Could you help with this please? |
@mananjadhav, @Beamanator, @hoangzinh, @bfitzexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Quick bump @bfitzexpensify 😬 👍 |
Sorry for the delay here 😅. Reposted the job on Upwork and sent out offers. I agree with adding this as a regression test and using the test steps for that - will get on to that tomorrow! |
@bfitzexpensify This PR is not eligible for timeline bonus. Can you resend the offer without the timeline bonus? Payout for the PR amount only. |
Thanks @bfitzexpensify for the payout here. |
@bfitzexpensify I got 2 offers, when I click in both of offers, it's saying "This offer is not available anymore" |
@hoangzinh Hm, I'm seeing this: I reposted the job and tried to invite you again and got the same response. Can you please apply to it here? |
@bfitzexpensify sorry for this inconvenient, my upwork account is on hold. I have to verify my ID first. Can we wait for couple of days please? |
Yes, no problem! The job will remain open, just let me know here when you apply to it. |
Hi @bfitzexpensify I have resolved my upwork account. It's back to normal now. I have applied to the job in Upwork according to suggestion here #15634 (comment). Do you happen to send me another offer again? Thank you so much. |
@hoangzinh offer sent! |
Issue to update regression test here - https://github.com/Expensify/Expensify/issues/277366 |
@bfitzexpensify accepted offer. Thank you |
Great, all payments now complete. |
@mananjadhav, @Beamanator, @hoangzinh, @bfitzexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@bfitzexpensify looks like payments have been made, yeah? Closing this out for now, feel free to reopen if needed 👍 |
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:
(In the video watch "jimmy" name was bold when he sent message when i switch to other app it will not remain bold)
Expected Result:
Every one's name should remain bold even if i switch to the other app
Actual Result:
One of the user name not remain bold after switching to other app
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.78-0
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:
20230214222649.mp4
mobizen_20230302_131644.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1676397495296059
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: