Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix video replay issue in iOS #38419

Merged
merged 5 commits into from
Apr 2, 2024
Merged

Fix video replay issue in iOS #38419

merged 5 commits into from
Apr 2, 2024

Conversation

ShridharGoel
Copy link
Contributor

@ShridharGoel ShridharGoel commented Mar 15, 2024

Details

Fix video replay issue in iOS.

Fixed Issues

$ #37249
PROPOSAL: #37249 (comment)

Tests

  1. Open a video attachment.
  2. Let the video play in normal mode.
  3. Try to play/pause a few times.
  4. Once the video completes, try to replay it.
  5. Do the same (steps 2-4) for fullscreen mode.
  • Verify that no errors appear in the JS console

QA Steps

  1. Open a video attachment.
  2. Let the video play in normal mode.
  3. Try to play/pause a few times.
  4. Once the video completes, try to replay it.
  5. Do the same (steps 2-4) for fullscreen mode.
  • 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)
  • [ x 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
Screen.Recording.2024-04-03.at.12.47.23.AM.mov
Android: mWeb Chrome
Screen.Recording.2024-04-03.at.1.35.46.AM.mov
iOS: Native
Screen.Recording.2024-04-03.at.12.56.59.AM.mov
iOS: mWeb Safari
Screen.Recording.2024-04-03.at.1.31.00.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2024-04-02.at.9.56.40.PM.mov
MacOS: Desktop
Screen.Recording.2024-04-02.at.9.59.45.PM.mov

@ShridharGoel ShridharGoel requested a review from a team as a code owner March 15, 2024 19:33
@melvin-bot melvin-bot bot removed the request for review from a team March 15, 2024 19:33
Copy link

melvin-bot bot commented Mar 15, 2024

@mananjadhav 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]

@melvin-bot melvin-bot bot requested a review from mananjadhav March 15, 2024 19:33
@mananjadhav
Copy link
Collaborator

@ShridharGoel I understand the impacted platform is just iOS. But considering the change is in BaseVideoPlayer, can we please add test videos for all the platforms? We don't want any regressions because of this change.

@ShridharGoel
Copy link
Contributor Author

@mananjadhav Added for other platforms as well, apart from Android native. Will add that also soon.

@ShridharGoel
Copy link
Contributor Author

@mananjadhav All videos have been added.

@mananjadhav
Copy link
Collaborator

Thanks for the update @ShridharGoel. While the code changes look good, I need to check if adding isPlaying dependency causes any further issues. Please allow a day for me to test these scenrios.

@ShridharGoel
Copy link
Contributor Author

@mananjadhav Gentle bump on this.

@mananjadhav
Copy link
Collaborator

@ShridharGoel Can we elaborate the test steps to also add the full-screen mode?

@mananjadhav
Copy link
Collaborator

@ShridharGoel I am still seeing some issues when I click on the Play button.

Screen.Recording.2024-03-23.at.1.14.32.AM.mov

@ShridharGoel
Copy link
Contributor Author

@mananjadhav I didn't get the issue from the video that you've attached. Shouldn't the play button be clicked after video is complete to check this?

@mananjadhav
Copy link
Collaborator

Yes the center play button to be clicked in the full screen mode after the video is complete.

@mananjadhav
Copy link
Collaborator

fyi I just followed the steps mentioned in the issue reproduction steps.

@ShridharGoel
Copy link
Contributor Author

ShridharGoel commented Mar 24, 2024

@mananjadhav Can you check once again if your build was having the changes from my branch? It was working correctly for me.

@mananjadhav
Copy link
Collaborator

@ShridharGoel I had tried in your branch only with the latest main at that point of time. I'll take a look at my end again, but can we merge the latest main and try once again?

Can you upload the screencast of the iOS along with the steps you performed?

@ShridharGoel
Copy link
Contributor Author

ShridharGoel commented Mar 29, 2024

@mananjadhav Video with updated main

Screen.Recording.2024-03-29.at.12.45.29.PM.mov

@mananjadhav
Copy link
Collaborator

Hmm. Thanks for the video, I'll take a look.

@mananjadhav
Copy link
Collaborator

mananjadhav commented Mar 31, 2024

@ShridharGoel It worked this time on iOS but not on the web. Clicking on the center of the video doesn't play/pause the video. It glitches and then continues to play.

web-playback-error_oa2p66ub.mp4

I think for all the platforms, we should be doing a thorough testing for all play-pause controls, the buttons, the screen, full screen mode, and play-pause end of the video, middle of the video.

Also, can we improve the content of the Test steps? Let's include, the part for fullscreen and also mention that we should hit Play-Pause a few times when the video is played.

@ShridharGoel
Copy link
Contributor Author

@mananjadhav shouldReplayVideo always returns false for web. This change shouldn't affect that.

@mananjadhav
Copy link
Collaborator

@mananjadhav shouldReplayVideo always returns false for web. This change shouldn't affect that.

I tested this against the staging env and latest main. Can you confirm at your end?

@ShridharGoel
Copy link
Contributor Author

@mananjadhav Should we remove isPlaying from the dependencies of useCallback? It doesn't seem needed.

@ShridharGoel
Copy link
Contributor Author

ShridharGoel commented Apr 2, 2024

@mananjadhav I've removed the isPlaying dependency, can you check again?

@mananjadhav
Copy link
Collaborator

I checked on Web it worked fine, but I'll need time to test all platforms.

I think for all the platforms, we should be doing a thorough testing for all play-pause controls, the buttons, the screen, full screen mode, and play-pause end of the video, middle of the video.

Can you please update your screencasts to cover. This is to ensure we don't add any regression.

Also, can we improve the content of the Test steps? Let's include, the part for fullscreen and also mention that we should hit Play-Pause a few times when the video is played.

And can you also update the Test steps as requested earlier?

@ShridharGoel
Copy link
Contributor Author

Updated description. Will add the videos in few hours.

@mananjadhav
Copy link
Collaborator

Thanks, just post a comment once the videos are uploaded. I think I'll also be able to test by that time. Thank you for your patience.

@mananjadhav
Copy link
Collaborator

mananjadhav commented Apr 2, 2024

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
android-video-replay.mov
Android: mWeb Chrome
mweb-chrome-video-replay.mov
iOS: Native
ios-video-replay.mov
iOS: mWeb Safari
mweb-safari-video-replay.mov
MacOS: Chrome / Safari
web-video-replay_2ddspBnh.mp4
MacOS: Desktop
desktop-video-replay_0ksQDmtJ.mp4

@melvin-bot melvin-bot bot requested a review from cead22 April 2, 2024 18:37
@@ -127,6 +127,7 @@ function BaseVideoPlayer({
videoStateRef.current = e;
onPlaybackStatusUpdate(e);
},
// eslint-disable-next-line react-hooks/exhaustive-deps
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment explaining why we're not adding all the deps?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added.

@ShridharGoel
Copy link
Contributor Author

@mananjadhav New videos have been added.

@@ -127,6 +127,7 @@ function BaseVideoPlayer({
videoStateRef.current = e;
onPlaybackStatusUpdate(e);
},
// eslint-disable-next-line react-hooks/exhaustive-deps -- we don't want to trigger this when isPlaying changes because isPlaying is only used inside shouldReplayVideo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💚

@cead22 cead22 merged commit 0ca78c3 into Expensify:main Apr 2, 2024
17 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Apr 2, 2024

✋ 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
Copy link
Contributor

OSBotify commented Apr 8, 2024

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.60-13 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants