-
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-10-10] [HOLD for payment 2023-10-09] [$500] Chat - Error appears on click of notification and does not redirect to page #28328
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01d1b259b2d9260fc0 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Error shows in console after tapping notification and does not navigate as expected. What is the root cause of that problem?The notification is using a function that is no longer there. What changes do you think we should make in order to solve the problem?The function was moved from App/src/libs/actions/Report.js Lines 1652 to 1656 in 13b2291
What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
ProposalPlease re-state the problem that we are trying to solve in this issue.DEV: Chat - Error appears on click of notification and does not redirect to page What is the root cause of that problem?This is a regression from this PR #28050 App/src/libs/actions/Report.js Line 1686 in bfda42d
What changes do you think we should make in order to solve the problem?just we have to update here App/src/libs/actions/Report.js Line 1686 in bfda42d
like this - onClick: () => Navigation.navigate(ROUTES.getReportRoute(reportID))
+ onClick: () => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(reportID)) What alternative solutions did you explore? (Optional) |
I'm having trouble understanding what's the proposed solution. Could you try rephrasing it? |
TL;DR: The function Thanks for asking for clarification! It's pretty much the same as @Charan-hs 's proposal. I just had the changes ( |
Proposal |
Issue in staging now, changing status of report to Deploy Blocker |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @johnmlee101 ( |
@redpanda-bit's proposal looks good to me. Please raise a PR asap |
On it @s77rt. |
This is regression from #27299, not from #28050. |
Going through PR checklist still. |
Is anyone available to help me test the platforms I am missing?
Or is it ok this time since the change is only a one liner? |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 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-10-09. 🎊 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.
For reference, here are some details about the assignees on this issue:
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:
|
|
@cubuspl42 Sorry I didn't mean to take the C+ role. Just wanted to push this since it was a deploy blocker. Please apply in the Upwork job instead. |
@s77rt No need; you did the actual job. If it was a deploy blocker, that was the right way to proceed. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.76-6 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-10-10. 🎊 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.
For reference, here are some details about the assignees on this issue:
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:
|
Checklist filled already in #28328 (comment) |
Switching this to daily so that I can issue payment this week. |
Payment Summary:
@s77rt requires - $500 - 50%(regression) = $250 |
@flaviadefaria This did not cause a regression (it was a regression from another PR). No penalties here. |
Thanks @s77rt, here's the updated Payment Summary: For reference, here are some details about the assignees on this issue: @s77rt requires - $500 Issuing payment now. |
@s77rt requires - offer sent |
@redpanda-bit offer sent! |
@s77rt requires - offer sent @s77rt please accept the offer so that I can pay you and close this GH. |
@flaviadefaria No payment is due for me here. Just wanted to resolve the deploy blocker. This can be closed. |
Ah, thanks for clarifying - closing! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
It should redirect to userA chat
Actual Result:
Nothing happens on click of notification and console error appears (ROUTES__WEBPACK_IMPORTED_MODULE_13_.default.getReportRoute is not a function)
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: Dev 1.3.74-2
Reproducible in staging?: n
Reproducible in production?: n
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: Any additional supporting documentation
Screen.Recording.2023-09-26.at.11.58.34.AM.1.mov
Screen.Recording.2023-09-28.at.11.06.03.AM.mov
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695709767898199
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: