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
{{ message }}
Repository navigation
Search - No results triggered when searching for valid words in chat search. #56028
Version Number: 9.0.92-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):ibellicotest+227@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome App Component: Search
Action Performed:
Open the staging.new.expensify.com website.
Open any chat.
Send some messages to the chat.
Tap on the search icon on the top right corner.
Tap on "Search in this chat"
Write a word that should trigger results.
Expected Result:
Correct content should be displayed after the user searches for any word included in a conversation.
Actual Result:
No results are triggered after the user searches for valid words in chat search.
👋 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.
@luacmartins I tested this across various chats and it seems to be working for most except the workspace chat, I looked at the response data for WS chat and it seems like backend is not returning anything. Would you want to take over this?
I'm unable to reproduce this issue in the selfDM like shown in the OP. As for the workspace chat, like @techievivek mentioned, that's the expected behavior because in the Workspace chat the default behavior is searching for expenses, not chats. So you'd have to change the type to chat to see the results. When I do that, I can find them without issues.
Activity
melvin-bot commentedon Jan 30, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 30, 2025
Triggered auto assignment to @isabelastisser (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Jan 30, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 30, 2025
👋 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:
techievivek commentedon Jan 30, 2025
We can certainly demote this since it seems to be working all chats but workspace.
techievivek commentedon Jan 30, 2025
@luacmartins I tested this across various chats and it seems to be working for most except the workspace chat, I looked at the response data for WS chat and it seems like backend is not returning anything. Would you want to take over this?
luacmartins commentedon Jan 30, 2025
Yea, I can look into this
melvin-bot commentedon Feb 3, 2025
@luacmartins, @isabelastisser Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
isabelastisser commentedon Feb 4, 2025
any updates here, @luacmartins thank you!
luacmartins commentedon Feb 4, 2025
Not yet, I'll look into it this week
luacmartins commentedon Feb 5, 2025
I'm unable to reproduce this issue in the selfDM like shown in the OP. As for the workspace chat, like @techievivek mentioned, that's the expected behavior because in the Workspace chat the default behavior is searching for expenses, not chats. So you'd have to change the type to chat to see the results. When I do that, I can find them without issues.
Gonna close this issue. Please reopen if needed.