Search Issue Tracker
By Design
By Design in 1.8.X
Votes
0
Found in [Package]
1.8.7
Issue ID
BUR-2482
Regression
Yes
"Failed to find entry-points" error after asset importing when the DLL files are named differently than their assemblies
Reproduction steps:
1. Open the attached project “StandaloneProfilerBugs”
2. Check the Console window
Expected results: There are no messages in the Console window
Actual result: An error is thrown saying “Failed to find entry-points:” in the Console window
Reproducible with: 1.8.0-pre.2 (2021.3.29f1), 1.8.7 (2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b4)
Not reproducible with: 1.8.0-pre.1 (2021.3.29f1)
Reproducible on: macOS 13.4.1 (c)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Unity generally does not support assembly names that differs from the DLL names. UnityLinker and IL2CPP, in particular, do not support it either.
Resolution Note (1.8.X):
Unity generally does not support assembly names that differs from the DLL names. UnityLinker and IL2CPP, in particular, do not support it either.