Skip to content

[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

Closed

Description

@kbecciv

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:

  1. From userA, send message to userB
  2. From userB, click on the notification

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?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari -requested
  • MacOS / Desktop

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
  • Upwork Job URL: https://www.upwork.com/jobs/~01d1b259b2d9260fc0
  • Upwork Job ID: 1707070231351926784
  • Last Price Increase: 2023-09-27
  • Automatic offers:
    • s77rt | Reviewer | 26983371
    • gadhiyamanan | Reporter | 26983373

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Sep 27, 2023
  2. changed the title [-]DEV: Chat - Error appears on click of notification and does not redirect to page[/-] [+][$500] DEV: Chat - Error appears on click of notification and does not redirect to page[/+] on Sep 27, 2023
  3. melvin-bot commented on Sep 27, 2023

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Sep 27, 2023
  5. melvin-bot commented on Sep 27, 2023

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 (External)

  6. carlosalmonte04 commented on Sep 27, 2023

    @carlosalmonte04
    Contributor

    Proposal

    Please 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 ROUTES.getReportRoute(reportID) to ROUTES.REPORT_WITH_ID.getRoute(reportID)

    App/src/libs/actions/Report.js

    Lines 1652 to 1656 in 13b2291

    const notificationParams = {
    report,
    reportAction,
    onClick: () => Navigation.navigate(ROUTES.getReportRoute(reportID)),
    };

    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.

  7. Charan-hs commented on Sep 28, 2023

    @Charan-hs
    Contributor

    Proposal

    Please 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
    In this PR refactored ROUTES.ts here and failed to update here

    onClick: () => Navigation.navigate(ROUTES.getReportRoute(reportID)),

    What changes do you think we should make in order to solve the problem?

    just we have to update here

    onClick: () => Navigation.navigate(ROUTES.getReportRoute(reportID)),

    like this

    - onClick: () => Navigation.navigate(ROUTES.getReportRoute(reportID))
    + onClick: () => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(reportID))

    What alternative solutions did you explore? (Optional)

  8. jakub-trzebiatowski commented on Sep 29, 2023

    @jakub-trzebiatowski
    Contributor

    @redpanda-bit

    The function was moved from ROUTES.REPORT_WITH_ID.getRoute(reportID) toROUTES.getReportRoute(reportID)

    I'm having trouble understanding what's the proposed solution. Could you try rephrasing it?

  9. carlosalmonte04 commented on Sep 29, 2023

    @carlosalmonte04
    Contributor

    TL;DR: The function ROUTES.getReportRoute(reportID) no longer exists and the function calls to this function need to be updated to ROUTES.REPORT_WITH_ID.getRoute(reportID)

    Thanks for asking for clarification!

    It's pretty much the same as @Charan-hs 's proposal. I just had the changes (from -> to) backwards because of rushing to be the first proposal. I think both proposals achieve the exact same result.

  10. carlosalmonte04 commented on Sep 29, 2023

    @carlosalmonte04
    Contributor

    Proposal

    Updated

  11. removed
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Sep 29, 2023
  12. 59 remaining items

  13. added and removed on Oct 9, 2023
  14. flaviadefaria commented on Oct 11, 2023

    @flaviadefaria
    Contributor

    Payment Summary:

    For reference, here are some details about the assignees on this issue:
    @s77rt requires payment offer (Reviewer)
    @redpanda-bit requires payment
    @gadhiyamanan requires payment offer (Reporter)

    @s77rt requires - $500 - 50%(regression) = $250
    @redpanda-bit - $500 - 50%(regression) = $250
    @gadhiyamana - $50 (reporter)

  15. s77rt commented on Oct 11, 2023

    @s77rt
    Member

    @flaviadefaria This did not cause a regression (it was a regression from another PR). No penalties here.

  16. flaviadefaria commented on Oct 12, 2023

    @flaviadefaria
    Contributor

    Thanks @s77rt, here's the updated Payment Summary:

    For reference, here are some details about the assignees on this issue:
    @s77rt requires payment offer (Reviewer)
    @redpanda-bit requires payment
    @gadhiyamanan requires payment offer (Reporter)

    @s77rt requires - $500
    @redpanda-bit - $500
    @gadhiyamana - $50 (reporter)

    Issuing payment now.

  17. flaviadefaria commented on Oct 12, 2023

    @flaviadefaria
    Contributor

    @s77rt requires - offer sent
    @redpanda-bit - please share your UW profile link since I can't find you to send an offer
    @gadhiyamana - $50 (reporter) - paid

  18. carlosalmonte04 commented on Oct 12, 2023

    @carlosalmonte04
    Contributor
  19. flaviadefaria commented on Oct 12, 2023

    @flaviadefaria
    Contributor

    @redpanda-bit offer sent!

  20. flaviadefaria commented on Oct 12, 2023

    @flaviadefaria
    Contributor

    @s77rt requires - offer sent
    @redpanda-bit - paid
    @gadhiyamana - paid

    @s77rt please accept the offer so that I can pay you and close this GH.

  21. s77rt commented on Oct 12, 2023

    @s77rt
    Member

    @flaviadefaria No payment is due for me here. Just wanted to resolve the deploy blocker. This can be closed.

  22. flaviadefaria commented on Oct 12, 2023

    @flaviadefaria
    Contributor

    Ah, thanks for clarifying - closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions