Skip to content

Resolve android corrupted recordings #1836

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

Conversation

jawad1257
Copy link
Contributor

The current stop function does not wait for the recording process to fully stop before proceeding. This can lead to corrupted files, as the audio or video thread may still be accessing the file when the app attempts to move it to the user's Movies directory. This MR updates the stop function to ensure it waits for the recording to completely stop, preventing file corruption.

@jawad1257
Copy link
Contributor Author

@daniel-g-favoreto-opl @bantunes22. @cloudwebrtc
Can you guys kindly review this?

@jawad1257 jawad1257 force-pushed the resolved-android-corrupted-recordings branch from 630ad4b to ecade84 Compare May 13, 2025 07:43
@cloudwebrtc
Copy link
Member

cloudwebrtc commented May 13, 2025

hey @jawad1257 , The code modification looks good, but can you please remove the license at the top of the code line? Generally speaking, when you create a PR, it means that you contribute this PR to flutter-webrtc and will follow the MIT license to share the modification with everyone else. and your changes will be recorded in the PR or new version CHANGELOG.

@jawad1257 jawad1257 force-pushed the resolved-android-corrupted-recordings branch from ecade84 to eb6cd21 Compare May 13, 2025 08:15
@jawad1257
Copy link
Contributor Author

@cloudwebrtc i was able to condense it down to one line. But because of the MIT we need to add this.

Copy link
Member

@cloudwebrtc cloudwebrtc left a comment

Choose a reason for hiding this comment

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

lg!

@cloudwebrtc cloudwebrtc merged commit 86dac0c into flutter-webrtc:main May 13, 2025
8 checks passed
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.

2 participants