Incorrect video downloaded #40647 #41054

superdev100 · 2024-04-26T02:46:38Z

Details

Fixed Issues

$ #40647
PROPOSAL: #40647 (comment)

Tests

Upload two videos
Play video 1
Play video 2
Open three dot menu of video 1 and press Download
Check that video 1 is downloaded.

Verify that no errors appear in the JS console

Offline tests

Same as tests
(Since this is download issue we can't test in offline status)

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

bandicam.2024-04-28.00-19-02-611.mp4

MacOS: Desktop

bandicam.2024-04-28.06-52-46-106.mp4

melvin-bot · 2024-04-26T02:46:42Z

@rayane-djouah Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

rayane-d

Please complete the author checklist, Thanks!

superdev100 · 2024-04-28T04:31:39Z

@rayane-djouah
Since this error is only reproducible in MacOS chrome & desktop, I've added video for that platforms.
Thanks.

rayane-d · 2024-04-29T20:55:23Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2024-04-29.at.9.30.51.PM.mov

Android: mWeb Chrome

Screen.Recording.2024-04-29.at.9.32.46.PM.mov

iOS: Native

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-04-29.at.21.26.39.mp4

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-04-29.at.21.28.39.mp4

MacOS: Chrome / Safari

Screen.Recording.2024-04-29.at.9.18.56.PM.mov

MacOS: Desktop

Screen.Recording.2024-04-29.at.9.20.41.PM.mov

rayane-d · 2024-04-29T21:28:21Z

@KMichel1030, Please write "Same as tests" in Offline tests and QA Steps sections when they have the same steps

superdev100 · 2024-04-29T21:34:36Z

@rayane-djouah
I've updated comment. Could you please check?

rayane-d

LGTM, Thanks!

src/components/VideoPlayerContexts/VideoPopoverMenuContext.tsx

rayane-d · 2024-04-30T01:24:17Z

@KMichel1030, can you please apply the suggested changes?

superdev100 · 2024-04-30T02:17:11Z

@rayane-djouah
I've pushed changes.

OSBotify · 2024-04-30T17:04:31Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-05-01T03:02:10Z

🚀 Deployed to staging by https://github.com/blimpich in version: 1.4.69-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-05-02T13:05:45Z

🚀 Deployed to production by https://github.com/Beamanator in version: 1.4.69-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

jayeshmangwani · 2024-06-27T13:50:34Z

src/components/VideoPlayerContexts/VideoPopoverMenuContext.tsx

+        if (typeof source === 'number' || !source) {
+            return;
+        }
+        const sourceURI = addEncryptedAuthTokenToURL(source.uri);


source.uri already has encryptedAuthToken appended. We are adding it again here,And because of this double encryptedAuthToken in the URL causes this issue: #43117 in Safari on mWeb.

@jayeshmangwani Does this mean we have to fix this issue again? Or did your follow up solution make sure to not cause a regression?

We have fixed the issue in a PR, comment was just to notify that we could have avoided this issue

sobitneupane · 2025-02-20T10:06:16Z

This case from this issue was missed while making the change in this PR.

Issue: Web - Attachments - Incorrect file format is downloaded when downloading video from preview
PR: https://github.com/Expensify/App/pull/56294/files

superdev100 added 2 commits April 25, 2024 06:00

fix download error

a4e8fe5

fix type error

7ffafd7

superdev100 requested a review from a team as a code owner April 26, 2024 02:46

melvin-bot bot removed the request for review from a team April 26, 2024 02:46

melvin-bot bot requested a review from rayane-d April 26, 2024 02:46

update ref name

50b3cb4

rayane-d suggested changes Apr 26, 2024

View reviewed changes

rayane-d approved these changes Apr 29, 2024

View reviewed changes

melvin-bot bot requested a review from blimpich April 29, 2024 21:52

blimpich requested changes Apr 29, 2024

View reviewed changes

src/components/VideoPlayerContexts/VideoPopoverMenuContext.tsx Outdated Show resolved Hide resolved

fix type issue

9415778

rayane-d approved these changes Apr 30, 2024

View reviewed changes

melvin-bot bot requested a review from blimpich April 30, 2024 11:01

blimpich approved these changes Apr 30, 2024

View reviewed changes

blimpich merged commit 4d9e102 into Expensify:main Apr 30, 2024

github-actions bot mentioned this pull request May 1, 2024

Deploy Checklist: New Expensify 2024-05-01 #41376

Closed

59 tasks

melvin-bot bot mentioned this pull request May 2, 2024

[HOLD for payment 2024-05-09] [$250] Incorrect video downloaded #40647

Closed

6 tasks

This was referenced May 2, 2024

Playback speed is not displayed correctly in video player #40646 #41055

Merged

[HOLD Waiting on contributor] [$250] Playing video is not paused when opening attachment modal. #40735

Closed

jayeshmangwani reviewed Jun 27, 2024

View reviewed changes

jayeshmangwani mentioned this pull request Jun 27, 2024

[HOLD for payment 2024-06-28] [$250] mWeb - Video - Download option is not working #43117

Closed

6 tasks

sobitneupane mentioned this pull request Feb 20, 2025

[AWAITING CHECKLIST][Due for payment 2025-02-18] [$250] Web - Attachments - Incorrect file format is downloaded when downloading video from preview #55541

Closed

8 tasks

Incorrect video downloaded #40647 #41054

Incorrect video downloaded #40647 #41054

Uh oh!

Conversation

superdev100 commented Apr 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Apr 26, 2024

Uh oh!

rayane-d left a comment

Choose a reason for hiding this comment

Uh oh!

superdev100 commented Apr 28, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rayane-d commented Apr 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

rayane-d commented Apr 29, 2024

Uh oh!

superdev100 commented Apr 29, 2024

Uh oh!

rayane-d left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

rayane-d commented Apr 30, 2024

Uh oh!

superdev100 commented Apr 30, 2024

Uh oh!

OSBotify commented Apr 30, 2024

Uh oh!

OSBotify commented May 1, 2024

Uh oh!

OSBotify commented May 2, 2024

Uh oh!

jayeshmangwani Jun 27, 2024

Choose a reason for hiding this comment

Uh oh!

blimpich Jun 27, 2024

Choose a reason for hiding this comment

Uh oh!

jayeshmangwani Jun 27, 2024

Choose a reason for hiding this comment

Uh oh!

sobitneupane commented Feb 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

superdev100 commented Apr 26, 2024 •

edited

Loading

superdev100 commented Apr 28, 2024 •

edited

Loading

rayane-d commented Apr 29, 2024 •

edited

Loading

sobitneupane commented Feb 20, 2025 •

edited

Loading