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
- "Assertion failed on expression" errors appear when selecting specific Tile Palette GameObjects
- “CommandBuffer: built-in render texture type 3 not found while executing” warning is displayed in URP project
- Player build logs a "material with shader doesn't have a '_MainTex' property" error when instantiating a specific amount of specific prefabs
- The LayerMask parameter is ignored when using Physics2D.GetRayIntersection method
- The Tilemap GameObject causes other Tilemap GameObjects to become invisible when its “Mask Interaction” is set to “Visible Inside Mask”
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.