Fix: Unreported IOException on MediaMetadataRetriever.release() with target SDK 33 (Android) #398
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
denisbevilacqua
changed the title
…e() with target SDK 33
denisbevilacqua
force-pushed
the
fix_metadata_release_ioexception
branch
from
5fab136
to
73d03b1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've updated the target SDK version to 33 in my React Native application. However, while building, Gradle raises concerns regarding an unreported IOException stemming from the execution of
MediaMetadataRetriever.release().The exception was added in API level 33.
I believe that incorporating a try-catch block would be the most prudent approach in this situation. This way, if an exception is thrown during the release process for any unforeseen reason (such as if the system has already initiated the release), the application will avoid crashing. I would like to mention that this approach has been tested, and now the app compiles successfully.
Closes #372