Reproduction steps:
- Open the user’s attached project
- Build And Run on an Android device
- Test all four options from the drop-down
Expected result: The path with “file://” scheme will open
Actual result: The path with “file://” scheme won’t open
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b9, 2023.1.0a13
Reproducible with devices:
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00099, Google Pixel XL (Pixel XL), Android 10, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Reproduced on: Windows 10 Pro 21H2
Notes:
- Android Logcat shows lots of
2022.07.20 16:41:53.347 18088 18217 Verbose NuMediaExtractor NuMediaExtractor destructor
2022.07.20 16:41:53.378 18088 18201 Verbose NuMediaExtractor NuMediaExtractor constructor
2022.07.20 16:41:53.381 18088 18201 Error NdkMediaExtractor can't create http service
2022.07.20 16:41:53.381 18088 18201 Warn Unity AndroidVideoMedia: Error opening extractor: -10002
- The SampleScene copies a WebM/vp8 file to a different path
- It only works on Android without the “file://” scheme
- Note that other file formats on Android work well with the “file://” scheme (e.g. mp4)
- Note that it also works on Windows and other platforms with the “file://” scheme
- Workaround: when having a vp8/WebM file on Android, set VideoPlayer.url without “file://” scheme
- Related forum post: https://forum.unity.com/threads/videoplayer-url-issue-with-vp8-webm-on-android-androidvideomedia-error-opening-extractor-10002.1255434/#post-7978743
- vp8 file opens with “file://” scheme on Samsung Galaxy XCover4 (SM-G390F) device