Search Issue Tracker
By Design
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.