Search Issue Tracker
Won't Fix
Votes
7
Found in [Package]
1.11.2
Issue ID
ADDR-1688
Regression
Yes
[Addressables] "RuntimeData is null" error in Build is thrown when AssetRefference.LoadAssetAsync<> is called in an async method
How to reproduce:
1. Open the user's attached project ("case_1299334-AddressablesBug.zip")
2. Build and Run
3. Click the "Load" button
Expected results: Both in the Editor and in the Build when calling LoadAssetAsync<> in an async method it does not throw any errors
Actual results: In the Build when calling LoadAssetAsync<> in an async method "RuntimeData is null. Please ensure you have built the correct Player Content." is thrown and a few more following errors (attached in "Player.log")
Reproducible with: Addressables 1.11.2 - 1.16.15 (2019.4.17, 2020.1.17, 2020.2.1f1, 2021.1.0b1)
Does not reproduce with: Adressables 1.8.5 - 1.10.0 (2019.4.17, 2020.1.17, 2020.2.1f1, 2021.1.0b1)
Could not test with: 2018.4.30f1
Note: with IL2CPP "MissingMethodException: Default constructor not found for type UnityEngine.ResourceManagement.AsyncOperations.ProviderOperation" is thrown, see "PlayerIL2CPP.txt"
-
dr4
Mar 02, 2023 12:59
Still happens in 2023, addressable do not work properly in build sometimes
-
nrader95
Nov 30, 2021 14:07
Same error here on 2020.3.f11 with both adressables 1.16 and old 1.8 branch.
So downgrading to older version still allow for bug to be reproduced.Building addressables directly before starting the build (with Assets Management - Addresables - Groups - Build - New Build - Default Build Script), however, helps. So the project build button doesn't seem to always start building addresables automatically, it seems.
-
noobogami
Sep 27, 2021 11:46
same here! with IL2CPP have this error and it appears randomly!
System.MissingMethodException: Default constructor not found for type UnityEngine.ResourceManagement.AsyncOperations.ProviderOperation`1[[UnityEngine.AddressableAssets.Initialization.ResourceManagerRuntimeData, Unity.Addressables, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]]
I have build that everything is fine then do another build without any changes and addressable explodes!
-
thecloudkeeper
Aug 25, 2021 20:16
Addressables are still broken. Date: 08/25/21. Unity version 2021.1.3f1. This is not fixed. Please re-open this issue.
-
Play2D
May 03, 2021 07:31
Happens in Unity 2020.3.6f1 using Addressables 1.18.2
So, no... it's not fixed.
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
- Symlinks are broken when a package which contains .xcframework + symlinks is added through Unity Package Manager.
- Crash on ApplyMaterialPass when opening a specific scene
- Memory leak when using Native Plugin in Windows IL2CPP Build
- [URP][Tutorial] Universal 3D Sample tutorial issues
- Gradle error: "...Unexpected error during link..." is thrown when building for Android and targeting API Level 34
Resolution Note:
Not a bug, my mistake