Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.5.1
1.6.2
Issue ID
ADDR-1043
Regression
No
[Addresables] Addressables causes "Unknown error in AsyncOperation" when built to Android
How to reproduce:
1. Open the SampleScene in the attached "-ReproAddresables.zip-" (use Test Bed.zip or see attached files instead) Project
2. Build and run it on an Android device
3. Check logcat by typing "adb logcat" into the cmd window
Expected Behaviour: No errors are present in the logcat file
Actual Behaviour: "Unknown error in AsyncOperation" is in the logs
Reproducible with(Unity versions): 2018.4.18f1, 2019.3.4f1, 2020.1.0a26
Reproducible with(Package versions): 1.5.1, 1.6.2
Note: The object is still loaded, however, the exception is thrown
Reproduced devices:
VLNQA00322, Huawei P30 Pro (VOG-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00270, Samsung Galaxy S10e (SM-G970F), Android 9, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00115, Sony Xperia Z3 (D6603), Android 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
https://github.cds.internal.unity3d.com/unity/Addressables/pull/344
With the above fix, Addressables errors aren't thrown anymore in project "case_1221331_builtByOGC.zip".
However, the customer's assets still aren't loaded on Android. According to logs, this problem doesn't seem related to the errors mentioned in this task.