Skip to content

[HOLD for payment 2024-08-02] [$250] Video - Change in playback speed is not reflected in thread report #42519

Description

@lanitochka17

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: 1.4.75-0
Reproducible in staging?: Y
Reproducible in production?: N
**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): natnael.expensify+3@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Navigate to a report
  2. Send a video
  3. Reply in a thread to the video
  4. Navigate back to the main report
  5. Change playback speed
  6. Navigate to the thread report
  7. Click on 'Three dots' > 'Playback speed'

Expected Result:

Changes in Playback speed from the main report should be reflected in the thread report

Actual Result:

Changes in playback speed from the main report is not reflected in the thread report

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

Add any screenshot/video evidence

Bug6489315_1716463467872.Screen_Recording_2024-05-23_at_12.41.26_in_the_afternoon.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01aa9734a896a98cbf
  • Upwork Job ID: 1793619475924013056
  • Last Price Increase: 2024-06-06
  • Automatic offers:
    • situchan | Reviewer | 102822043
    • tienifr | Contributor | 102822045
Issue OwnerCurrent Issue Owner: @situchan

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 23, 2024
  2. melvin-bot commented on May 23, 2024

    @melvin-bot

    Triggered auto assignment to @Julesssss (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on May 23, 2024

    @melvin-bot

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:

    1. If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
      • If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
    2. Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
      • You can adjust the urgency of the issue to better represent the gravity of the bug.
      • If the issue is super low priority, feel free to un-assign yourself.
      • Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
      • If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.

    Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.

  4. github-actions commented on May 23, 2024

    @github-actions
    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. lanitochka17 commented on May 23, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #vip-vsp

  6. lanitochka17 commented on May 23, 2024

    @lanitochka17
    Author

    @Julesssss FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  7. Julesssss commented on May 23, 2024

    @Julesssss
    Contributor

    Thanks.

    This should not block deploy IMO. Removing the label.

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 23, 2024
  9. 93 remaining items

  10. tienifr commented on Aug 5, 2024

    @tienifr
    Contributor

    The PR is ready for review cc @Julesssss @situchan

  11. mallenexpensify commented on Aug 14, 2024

    @mallenexpensify
    Contributor

    In the PR I'm not seeing that it was deployed to production.

    @situchan @tienifr , any idea what might be going on? I want to update the title to reflect the correct payment date

  12. mallenexpensify commented on Aug 17, 2024

    @mallenexpensify
    Contributor

    @situchan @tienifr 👀 on the comment above plz so I can get you paid (assuming it's needed)

  13. situchan commented on Aug 19, 2024

    @situchan
    Contributor

    There was bug on that deploy. Melvin didn't post deploy comment on all PRs in this checklist.
    cc: @Beamanator

  14. Beamanator commented on Aug 19, 2024

    @Beamanator
    Contributor

    Agreed 👍 I posted in the PR about it being deployed to prod here - #46800 (comment)

  15. mallenexpensify commented on Aug 20, 2024

    @mallenexpensify
    Contributor

    d;oh, sorry, I should have seen that comment.
    Contributor: @tienifr owed $250 via NewDot
    Contributor+: @situchan paid $250 via NewDot.

    @situchan plz complete the BZ checklist above? Thx

  16. situchan commented on Aug 21, 2024

    @situchan
    Contributor

    Regression Test Steps

    1. Send a video to any chat
    2. Reply the video in thread
    3. Navigate to parent report
    4. Change playback speed
    5. Navigate to thread
    6. Open playback speed menu
    7. Verify thread's playback speed is the same with parent's
  17. mallenexpensify commented on Aug 26, 2024

    @mallenexpensify
    Contributor
  18. garrettmknight commented on Aug 27, 2024

    @garrettmknight
    Contributor

    @tienifr paid $250 via NewDot

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions