Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.18
Issue ID
BUR-2799
Regression
Yes
"Failed to find entry-points" Burst error appears in the Console window when installing an asset containing a NETStandard2.0 assembly file
How to reproduce:
1. Open the attached "IN-89620" project
2. Observe the Console window
Expected result: Console does not display any errors
Actual result: Console displays a “Failed to find entry-points” Burst error
Reproducible in: 1.8.0-pre.2 (2022.2.1f1, 2023.1.0a26), 1.8.18 (2021.3.48f1, 2022.3.56f1, 6000.0.35f1, 6000.1.0b3)
Not reproducible in: 1.8.0-pre.1(2022.2.1f1, 2023.1.0a26)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
* Error is related to importing the “0Harmony.dll” file (can be found in the Assets/Plugins folder)
* Burst version 1.8.0-pre.2 displays a slightly different “Failed to find entry-points” Burst error than the full release package versions
* Error message appears each time when reloading the domain
Comments (1)
-
tim_jones
Feb 03, 2025 12:09
It looks like the resolution note didn't propagate across correctly. Here's what it was supposed to say:
This issue is caused by some invalid metadata in the "Fat" build of v2.3.3.0 of 0Harmony.dll. It looks like this dll is built with ILRepack, and it appears that ILRepack has incorrectly packed one of the type references - 01000126. If you open the dll with a tool like ILSpy, and look at the TypeReference metadata table for that type reference, you'll see it refers to an AssemblyReference that doesn't exist.
So in this case, Burst is "correctly" emitting an error message because of invalid metadata in this library.
We have tested with a locally-built "Fat" release build of Harmony, built from the latest code in the Harmony repo on GitHub (which is newer than v2.3.3.0). This works fine, so we suggest doing that as a workaround. You could also report it as a bug to Visual Scripting Enhancer, to ask them to update to the latest build of Harmony.
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note:
This issue is caused by some invalid metadata in the "Fat" build of v2.3.3.0 of 0Harmony.dll. It looks like this dll is built with ILRepack, and it appears that ILRepack has incorrectly packed one of the type references - 01000126. If you open the dll with a tool like ILSpy, and look at the TypeReference metadata table for that type reference, you'll see it refers to an AssemblyReference that doesn't exist.
So in this case, Burst is "correctly" emitting an error message because of invalid metadata in this library.
I have tested with a locally-built "Fat" release build of Harmony, built from the latest code in the Harmony repo on GitHub (which is newer than v2.3.3.0). This works fine, so I suggest doing that as a workaround. You could also report it as a bug to Visual Scripting Enhancer, to ask them to update to the latest build of Harmony.