Search Issue Tracker
Won't Fix
Votes
0
Found in
5.2.2f1
Issue ID
745298
Regression
No
[iOS] Asset Bundle build causes "Could not produce class with ID ..." errors when running the build on device
Reproduction steps:
1. Open the attached project "New Unity Project";
2. Open the aaa.unity scene;
3. Build the asset bundles of this scene (Assets->Build AssetBundles);
4. Open the Build settings of the project, choose iOS build and build the project;
5. Run the built project on the device (doesn't matter which one);
6. Observe the output in the Console.
Expected results: the built project is playing without any issues;
Actual results: after running, the Console displays several errors:
"Could not produce class with ID ..."
Reproduced on: 2017.1.3p4, 2017.2.2p4, 2017.3.2f1, 2017.4.2f2, 2018.1.0f2, 2018.2.0b2.
Tested with iPhone 5s (iOS 9.3.3) and iPhone 7 Plus 10.3.1.
Won't Fix: The case won't be fixed, as this issue has low user pain and is not planned to dedicate time and resources to fix this. The log does ask the user to try disabling Strip Engine Code.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment