Skip to content

Error When Sending a Message in a Thread #63019

Closed

Description

@m-natarajan

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:

  1. Go to a DM with another participant
  2. Go to a message sent from the other participant in the main DM
  3. Click “reply in thread” to create a thread
  4. 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:
Image
  • The debug info is super light:
Image

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

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on May 29, 2025
  2. melvin-bot commented on May 29, 2025

    @melvin-bot

    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.

  3. MelvinBot commented on May 29, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. trjExpensify commented on May 29, 2025

    @trjExpensify
    Contributor

    @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

  5. muttmuure commented on May 30, 2025

    @muttmuure
    Contributor

    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

  6. trjExpensify commented on May 30, 2025

    @trjExpensify
    Contributor

    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.

    • What type of chat report? Is it in the #admins room, a DM, a group, a room etc?
    • Were you a "member" of that thread already, or was this comment your action to try and join the thread? or start a thread maybe?
    • If you natively type in that URL with the reportID, does the thread appear or NotFound?
    • Did you enable Debug Mode and then go to the thread report > header > Debug > JSON to copy the OnyxData to grab those details to check participants and permissions of this report?
    • I take it the failing command is AddComment here, using the requestID and linking the logs would be helpful?
  7. trjExpensify commented on May 30, 2025

    @trjExpensify
    Contributor

    ^^ 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.

  8. trjExpensify commented on Jun 2, 2025

    @trjExpensify
    Contributor

    Chatted to Matt, adding the AutoAssignerQuality label for more eyes.

  9. 54 remaining items

  10. gedu commented on Jul 16, 2025

    @gedu
    Contributor

    I'm testing, not able to reproduce yet. Still checking the logs if I can find some pattern

  11. gedu commented on Jul 21, 2025

    @gedu
    Contributor

    I haven't been able to reproduce this issue yet

  12. gedu commented on Jul 23, 2025

    @gedu
    Contributor

    Cannot reproduce the error, and the logs don't show any related errors.

  13. mvtglobally commented on Jul 26, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (Fifth week) Are we ok to close?

  14. melvin-bot commented on Jul 28, 2025

    @melvin-bot

    @iwiznia, @gedu, @trjExpensify Huh... This is 4 days overdue. Who can take care of this?

  15. trjExpensify commented on Jul 29, 2025

    @trjExpensify
    Contributor

    @gedu @iwiznia @mountiny what shall we do with this issue as a next step?

  16. mountiny commented on Jul 29, 2025

    @mountiny
    Contributor

    I would personally just close at this point.

  17. trjExpensify commented on Jul 30, 2025

    @trjExpensify
    Contributor

    Works for me!

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

Metadata

Metadata

Labels

AutoAssignerNewDotQualityUsed to assign quality issues to engineersBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Needs ReproductionReproducible steps neededretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions