-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2024-06-20] [$250] Chat - Unable to open chat if going back from not found page after using send invoice link #42902
Comments
Triggered auto assignment to @madmax330 ( |
Triggered auto assignment to @isabelastisser ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@isabelastisser I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think this issue might be related to the #collect project. |
Production RPReplay_Final1717130534.MP4 |
Removed the deploy blocker as per this plan. Let's assign @tienifr to fix and @shubham1206agra for the c+ review, since they are the authors of the original PR 🙏 |
Taking a look. |
Job added to Upwork: https://www.upwork.com/jobs/~019eaddaf6970628b2 |
Current assignee @shubham1206agra is eligible for the External assigner, not assigning anyone new. |
@izarutskaya : i see that after multiple taps (randomly) the chat opens up and shows the page not found view. do you see the same behaviour? looking into the issue. |
@tienifr / @cristipaval : can you please point me to the original PR here? Thank you. |
@cristipaval : Is this already assigned to @tienifr as a regression issue? |
I opened PR above ^ |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.82-4 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 2024-06-20. 🎊 For reference, here are some details about the assignees on this 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:
|
Payment Summary
BugZero Checklist (@isabelastisser)
|
@shubham1206agra, please complete the BZ list above. Thanks! |
ROLE: c+ @shubham1206agra paid $250via Upwork @tienifr, can you please share your Upwork profile link? @shubham1206agra I sent you an offer. |
This comment was marked as outdated.
This comment was marked as outdated.
@isabelastisser I'm working with Dylan to enable myself to receive payments via NewDot. Could we hold paying me until after then, so it can be paid via NewDot? Thanks! |
@isabelastisser Sorry, but this issue was a regression and does not require any payment and checklist. |
Oh yes completely missed this. This is a regression. |
Thanks for the heads up! I will cancel @shubham1206agra offer in Upwork now. Closing. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.78-2
Reproducible in staging?: Y
Reproducible in production?: N
Found when executing PR : #41730
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
in any chat
Expected Result:
The chat is opened.
Actual Result:
Unable to open the chat, it is not responding to a tap. It seems like user should be navigated to the chat in the first place instead of the LHN when going back from the not found page.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6496964_1717122415517.video_2024-05-30_22-25-47.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @isabelastisserThe text was updated successfully, but these errors were encountered: