Repository navigation
Description
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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
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: AddComment logs
Expensify/Expensify Issue URL:
Issue reported by: @muttmuure
Slack conversation (hyperlinked to channel name): #Quality
Action Performed:
- Go to a DM with another participant
- Go to a message sent from the other participant in the main DM
- Click “reply in thread” to create a thread
- Add a comment
Expected Result:
Message should be sent successfully within the thread without errors.
Actual Result:
An error You don't have access to this chat room message appears, and the message fails to send.
Notes:
- The URL for the thread report when entered natively into the browser is not accessible either:
- The debug info is super light:
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
The Onyx data for the issue is in OP
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon May 29, 2025
Triggered auto assignment to @trjExpensify (
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.MelvinBot commentedon May 29, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
trjExpensify commentedon May 29, 2025
@muttmuure @m-natarajan did you link the wrong thread or something? The one linked wasn't reported by Matt and we have an issue for that thread here: #62643
muttmuure commentedon May 30, 2025
I'm not sure that's the same issue - this is for an error when sending a message in a chat thread. The URLs here are linked to the correct thread in Slack:
https://expensify.slack.com/archives/C05LX9D6E07/p1748422562528359
trjExpensify commentedon May 30, 2025
Oh, did Slack deep link me some place else? 😅 I can get to that slack thread now. I think this is a little light on information to try and repro, or rather, I don't know what someone is going to do with this issue as it is.
AddCommenthere, using the requestID and linking the logs would be helpful?trjExpensify commentedon May 30, 2025
^^ chatted through them in thread with Matt, and I've updated the OP with more details. Ultimately, we don't know what happened here - perhaps an issue with creating the thread.
I tried to repro a bunch in a test account and couldn't.
trjExpensify commentedon Jun 2, 2025
Chatted to Matt, adding the
AutoAssignerQualitylabel for more eyes.54 remaining items
gedu commentedon Jul 16, 2025
I'm testing, not able to reproduce yet. Still checking the logs if I can find some pattern
gedu commentedon Jul 21, 2025
I haven't been able to reproduce this issue yet
gedu commentedon Jul 23, 2025
Cannot reproduce the error, and the logs don't show any related errors.
mvtglobally commentedon Jul 26, 2025
Issue not reproducible during KI retests. (Fifth week) Are we ok to close?
melvin-bot commentedon Jul 28, 2025
@iwiznia, @gedu, @trjExpensify Huh... This is 4 days overdue. Who can take care of this?
trjExpensify commentedon Jul 29, 2025
@gedu @iwiznia @mountiny what shall we do with this issue as a next step?
mountiny commentedon Jul 29, 2025
I would personally just close at this point.
trjExpensify commentedon Jul 30, 2025
Works for me!