[iOS 14] Video assets does not work
See original GitHub issue🐛 Bug Report
Wait for iOS 14 GM and see if this is still an issue. This bug might be premature as it’s has been spotted in iOS 14 Beta 5.
Summary of Issue
Local video assets does not work:
-
in
test-suite
/MediaLibrary
the filerequire('../assets/big_buck_bunny.mp4')
is being loaded and fails on the line https://github.com/expo/expo/blob/581067249dbb121aa3a74221d97cd9c2643b4ceb/apps/test-suite/tests/MediaLibrary.js#L65 because for some unknown reasonMediaLibrary.createAssetAsync
that tries to create a video asset from the locally loaded file ends up with theThe operation couldn’t be completed. (Cocoa error -1.)
error in the file: https://github.com/expo/expo/blob/581067249dbb121aa3a74221d97cd9c2643b4ceb/packages/expo-media-library/ios/EXMediaLibrary/EXMediaLibrary.m#L151-L165 -
in
test-suite
/Video
some tests that are waiting for the<Video />
component to be mounted and thus fireonReadyForDisplay
callback are failing with timeout, because this event is not being called wheneversource = someLocalFile
.
Environment - output of expo diagnostics
& the platform(s) you’re targeting
Environment:
Expo CLI 3.24.2 environment info:
System:
OS: macOS 10.15.6
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
Yarn: 1.22.4 - ~/.nvm/versions/node/v12.16.1/bin/yarn
npm: 6.14.8 - ~/.nvm/versions/node/v12.16.1/bin/npm
IDEs:
Android Studio: 4.0 AI-193.6911.18.40.6626763
Xcode: 11.6/11E708 - /usr/bin/xcodebuild
npmPackages:
expo: ~39.0.0 => 39.0.0
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
expo-cli: 3.24.2
Phone:
iOS version: OS 14 Beta 5
Model: iPhone SE 2
Reproducible Demo
-
Open
test-suite
/MediaLibrary
and see all tests failing, because of -
Open
test-suite
/Video
and see some of the test that are waiting forfullscreen
events are failing.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
I set
shouldPlay
and it starts to play the video. The issue seems to be related to #2144This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.