Search Issue Tracker

By Design

Votes

0

Found in

2021.3.28f1

2022.3.4f1

Issue ID

UUM-41804

Regression

No

[ANDROID] Black screen in the Player when the video is loaded and played from the Asset Bundles

--

-

How to reproduce:
1. Open the "IN_45960" project
2. In the Build Settings "Run Device" dropdown select the desired device
3. Press Build And Run
4. Observe the Player

Expected result: video is playing in the Player
Actual result: black screen without the video playing in the Player

Reproducible with: 2021.3.28f1, 2022.3.4f1
Couldn't test with: 2023.1.3f1, 2023.2.0a21 (due to error "Error while evaluating property 'namespace' of task ':unityLibrary:packageDebugResources'.")

Testing environment: Windows 10 Pro

Reproducible on these devices:
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540

Not reproducible on these devices:
VLNQA00363, Samsung Galaxy Z Fold2 5G (SM-F916B), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: NOT FOUND, GPU: Mali-G76

Notes:
- User mentioned the issue is reproducible on Android 7 and Android 8 OS
- Not reproducible on Windows Standalone and WebGL
- Errors when built for WebGL Platform (asset bundle doesn’t seem to load in the first place but not the same issue as in Android)

  1. Resolution Note:

    Prior to Android 9.0, the Android media functionality shipped with the OS does not allow reading movie files using custom file readers such as what is required for reading from compressed or in-memory asset bundles. This means before Android 9.0, Unity is limited to playing movie files from uncompressed an and on-disk (not in-memory) asset bundles. This is explained in the documentation: https://docs.unity3d.com/Manual/android-requirements-and-compatibility.html

    To verify that this is what is happening, you can look at the device's logical and a message should explain the situation. It will look like this:

    AndroidVideoMedia::OpenExtractor could not translate <some path> to local file. Make sure file exists, is on disk (not in memory) and not compressed.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.