Skip to content

[HOLD for payment 2023-09-27] Unable to send attachment and new message is not shown in LHN after sending attachment #27163

Closed

Description

@kavimuru

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. Go to an existing conversation
  2. Click the plus icon -> Add attachment -> Choose from gallery
  3. Select any photo -> Send
  4. Then send a message to this chat

Expected Result:

The selected photo will be sent within seconds. The message sent should show in the LHN

Actual Result:

The selected photo is not sent. The message sent after not showing in the LHN

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari (@tgolen able to reproduce)
  • MacOS / Desktop

Version Number: 1.3.67-1
Reproducible in staging?: y
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

nganngok.mp4
az_recorder_20230911_112658.1.mp4

Expensify/Expensify Issue URL:
Issue reported by: @thuyle04
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694407887187689

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 11, 2023
  2. melvin-bot commented on Sep 11, 2023

    @melvin-bot

    Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Sep 11, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. OSBotify commented on Sep 11, 2023

    @OSBotify
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. melvin-bot commented on Sep 11, 2023

    @melvin-bot

    Triggered auto assignment to @jasperhuangg (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  6. pradeepmdk commented on Sep 11, 2023

    @pradeepmdk
    Contributor

    this is fixed here #24246 PR in review

  7. tgolen commented on Sep 11, 2023

    @tgolen
    Contributor

    I think the problem I was seeing is related to some of the pusher/https updates @danieldoglas and I have been making. I saw a console log for [SequentialQueue] Pausing the queue but it never became unpaused. There should eventually be a corresponding log like [SequentialQueue] Unpausing the queue and flushing 0 requests.

    I was able to log off refresh, and log back on and that fixed the issue for me now.

  8. jasperhuangg commented on Sep 11, 2023

    @jasperhuangg
    Contributor

    @tgolen Do you think we should be blocking deploy on this? Based on #24246 it also seems like this is a dupe.

  9. 28 remaining items

  10. thuyle04 commented on Sep 27, 2023

    @thuyle04

    @danieldoglas Do you have any payment for bug reporter, please?

  11. danieldoglas commented on Sep 28, 2023

    @danieldoglas
    Contributor

    @garrettmknight I just reassigned you, can you please deal with the bug reporter payment here?

  12. garrettmknight commented on Oct 4, 2023

    @garrettmknight
    Contributor
  13. thuyle04 commented on Oct 9, 2023

    @thuyle04

    @garrettmknight Hi, I can't access this url with my appropriate account.
    Screenshot from 2023-10-09 10-13-26

  14. garrettmknight commented on Oct 9, 2023

    @garrettmknight
    Contributor

    @thuyle04 sorry, the URL was for me!

    Summary of payments:

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions