Search Issue Tracker
Won't Fix
Won't Fix in 1.1.X
Votes
0
Found in [Package]
1.19.9
Issue ID
ADDR-2325
Regression
No
ScriptableObject in Scene loses serialised reference when releasing DownloadDependenciesAsync operation
Reproduction steps:
1. Open the "Main" project from the attached "case-1370530.zip" folder
2. Window > Asset Management > Addressables > Groups
3. From the "Play Mode Script" dropdown select "Use Existing Build"
4. From the "Build" dropdown select "New Build" > "Default Build Script"
5. Open the "Main" Scene
6. Enter Play Mode
7. Click the Button in the Game view
8. Repeat step 7
9. Observe the Console window
Expected result: No errors occurred
Actual result: "Cannot apply scene configuration in use: No performance profile selected" error is logged
Reproducible with: 1.18.9, 1.19.9 (2020.3.20f1, 2021.1.24f1, 2021.2.0b15, 2022.1.0a12)
Could not test with: 1.19.9 (2019.4.31f1), 1.18.4 (2020.3.20f1) - failed to load files errors after downgrade
Note:
- Error goes away when commenting out "downloadOperation.Completed += OnCompleteOperation;" (line 85) in Packages/com.btmain/Runtime/Main.cs
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This will not be fixed
Resolution Note (1.1.X):
Addressables is actually working as designed in this case. The scriptable object that was being used was part of one of the loaded asset bundles, so when new scenes were getting loaded (and previous scenes unload as a result) the AssetBundles were getting unloaded as well causing the reference to go missing.