You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hover over a message that was sent by a different user
Click on "Reply in thread"
Hover over the same root message from step 3
Click on "Flag as offensive"
Expected Result:
User is presented with different options to flag the message as offensive
Actual Result:
User is presented with an error - "Hmm... it's not here Oops, this page cannot be found".
Issue is not reproducible for thread root message if flag the message from chat view or if flag message other than root in thread view
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
MacOS / Desktop
Version Number: 1.3.43.2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
👋 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:
Identify the pull request that introduced this issue and revert it.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue found when executing PR #22831
Action Performed:
Expected Result:
User is presented with different options to flag the message as offensive
Actual Result:
User is presented with an error - "Hmm... it's not here Oops, this page cannot be found".
Issue is not reproducible for thread root message if flag the message from chat view or if flag message other than root in thread view
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.43.2
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
Bug6134927_Recording__783.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
The text was updated successfully, but these errors were encountered: