Search Issue Tracker
Duplicate
Votes
3
Found in [Package]
1.1.7
Issue ID
1177321
Regression
Yes
[Addressables] "Could not produce class" error is thrown in IL2CPP Build when using Custom Assets
Steps to reproduce:
1. Open user's attached project "AddressablesIssue.zip"
2. Build a project
3. Notice the error in the Developers Console "Could not produce class with ID 2089858493"
Expected results: Developers console does not throw errors in the build
Actual results: Developers console throw an error
Reproducible with: 2019.2.0a8(1.1.7), 2019.2.2f1(1.1.7), 2019.3.0a12(1.1.7)
Not Reproducible with: 2019.1.14f1(1.1.7), 2019.2.0a5(1.1.7)
Note: Builds with lower versions than 2019.2.0a6 do not produce such error, however, many other errors appear
[Addressables] "Could not produce class" errors in IL2CPP builds when using custom assets
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1190029