[HOLD for payment 2024-10-30] [$250] Workspace - "Refused to load media" console error when sending message offline in #announce

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.18-7
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4836807&group_by=cases:section_id&group_order=asc&group_id=229065
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Log in with a new Gmail account
3. Go offline
4. Click on the "Choose a workspace" button
5. Click on the "+" button to create a new workspace
6. Rename the workspace
7. Navigate to the #announce room
8. Send a message
9. Come online

Expected Result:

There shouldn't be a console error when sending the message.

Actual Result:

"Refused to load media" console error when sending a message offline in the #announce room. The error always happens when I send a message, and sometimes happens again when I come online.

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6566418_1723187972778.bandicam_2024-08-09_09-07-44-110.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021831809293142986687
• Upwork Job ID: 1831809293142986687
• Last Price Increase: 2024-09-26
• Automatic offers:
• rayane-djouah | Reviewer | 104235593
• wildan-m | Contributor | 104235594

Issue Owner

Current Issue Owner: @yuwenmemon

[melvin-bot]

Triggered auto assignment to @RachCHopkins (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.

[izarutskaya]

We think this issue might be related to the #vip-vsb

[melvin-bot]

@RachCHopkins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@RachCHopkins Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@RachCHopkins 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[RachCHopkins]

I don't see any error anywhere. Just that message in the console, so do we know what the message is telling us? Does the chat message send?

[RachCHopkins]

Can we get someone to replicate this @izarutskaya? Is there actually an error with the message sending, or is it completely restricted to the console?

[melvin-bot]

@RachCHopkins this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

@RachCHopkins Whoops! This issue is 2 days overdue. Let's get this updated quick!

[MelvinBot]

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

[RachCHopkins]

Still looking for some clarity on the problem for users.

[RachCHopkins]

Posted in QA channel

[mvtglobally]

Issue is still reproducible https://github.com/user-attachments/assets/19d076cf-b094-42f2-b7d0-6eef73e53ee4

[melvin-bot]

@RachCHopkins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[RachCHopkins]

Still trying to ascertain what the error is in reference to.

[RachCHopkins]

Ok so the issue appears to be that there is a stray error message in the console that means nothing.

[melvin-bot]

📣 @wildan-m 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[wildan-m]

@rayane-djouah PR is ready #50130 Thanks

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.52-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Resolves offline sound playback by caching assets locally #50130

If no regressions arise, payment will be issued on 2024-10-30. 🎊

For reference, here are some details about the assignees on this issue:

• @wildan-m requires payment automatic offer (Contributor)
• @rayane-djouah requires payment automatic offer (Reviewer)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@rayane-djouah] The PR that introduced the bug has been identified. Link to the PR:
• [@rayane-djouah] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@rayane-djouah] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@rayane-djouah] Determine if we should create a regression test for this bug.
• [@rayane-djouah] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@RachCHopkins] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[rayane-djouah]

BugZero Checklist

• The PR that introduced the bug has been identified. Link to the PR: feat: app sounds  #31055
• The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: feat: app sounds  #31055 (comment)
• A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
• Determine if we should create a regression test for this bug. Yes
• If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

1. Login and go to any chat
2. Go offline
3. Send a message
4. Verify that a sound can be heard
5. Go online
6. Send a message
7. Verify that a sound can be heard

Do we agree 👍 or 👎

[RachCHopkins]

Payment Summary:

Contributor: @wildan-m paid $250 via Upwork
Contributor+: @rayane-djouah paid $250 via Upwork
Upwork job here

[RachCHopkins]

Contributors have been paid, the contracts have been completed, and the Upwork post has been closed.

[melvin-bot]

@yuwenmemon @RachCHopkins Be sure to fill out the Contact List!

[RachCHopkins]

Looks like that might be one for you here @yuwenmemon - I don't think I'm "in the know" enough to complete that.

[melvin-bot]

@yuwenmemon, @wildan-m, @RachCHopkins, @rayane-djouah Huh... This is 4 days overdue. Who can take care of this?

[rayane-djouah]

@yuwenmemon bump on #47148 (comment)