-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[video-thumbnails][Android] Fix a crash when the source cannot be retrieved #28961
[video-thumbnails][Android] Fix a crash when the source cannot be retrieved #28961
Conversation
apps/native-component-list/src/navigation/ExpoComponentsStackNavigator.tsx
Outdated
Show resolved
Hide resolved
apps/native-component-list/src/screens/ExpoComponentsScreen.tsx
Outdated
Show resolved
Hide resolved
apps/native-component-list/src/screens/VideoThumbnailsScreen.tsx
Outdated
Show resolved
Hide resolved
apps/native-component-list/src/screens/VideoThumbnailsScreen.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Tomasz Sapeta <[email protected]>
Co-authored-by: Tomasz Sapeta <[email protected]>
Co-authored-by: Tomasz Sapeta <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for the contribution!
Do we know when this fix is going to be released to npm? I've patched my project's version of |
Hi @markrickert, |
@cristian0791 I don't have access to that client's source code anymore, but it should be relatively easy to make your own patch. just edit the two relevant files from this diff inside your node modules folder and run |
Why
Fixes #27936
How
sourceFilename
.sourceFilename
is valid, but the retriever can't load it due to a bad URI, then it throws an errorsetDataSource failed: status = 0x80000000
. To handle this, a catch handler is added.Test Plan
Tested using bare-expo.
Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).