Search Issue Tracker
Fixed in 1.1.9
Votes
0
Found in [Package]
0.8.6, 1.1.5
Issue ID
1169726
Regression
No
[Addressables] Built in Group can be marked as default, which causes NullReferenceException when building Player Bundles
How to reproduce:
1. Open the attached project ("case_1169726-LWRP-Asset-Bundles-Dependencies")
2. Try building Player Content
Expected results: Player Content is built successfully
Actual results: Player Content build fails with NullReferenceException
Reproducible with: 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Couldn't test with 2017.4, as it does not have Package Manager
Reproducible with package versions: 0.8.6, 1.1.5
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 1.1.9):
Users can still make Built In Data group default, but it no longer throws the Null Reference error when the user builds content.