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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
This is a duplicate of issue #1190029