Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2021.3.37f1
2022.3.24f1
2023.2.18f1
6000.0.0b14
Issue ID
UUM-69560
Regression
No
"DllNotFoundException" error is thrown in the Development Player when referencing a DLL plugin if the application path contains the ';' symbol
How to reproduce:
1. Open the “WinNativePlugin“ project
2. Open the “SampleScene“
3. Make sure to enable Development Build (File > Build Settings)
4. Make sure that the build path includes the ';' symbol
5. Build And Run
Expected result: The Player runs without errors
Actual result: The Player throws the “DllNotFoundException: TestPlugin assembly:<unknown assembly> type:<unknown type> member:(null)” error
Reproduced with: 2021.3.37f1, 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Reproduced on: macOS 14.3.1 (Intel) (by reporter), Windows 11, macOS 13.6.4 (M1), Ubuntu 20.04
Not reproduced on: No other environment tested
Notes:
1. Full error is provided in the internal comments
2. Not reproducible in the Editor
3. Not reproducible when development build is disabled
4. Not reproducible when the ';' symbol is not in the build path
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This issue is identified as an edge case. We have explored various workarounds; however, they were not effective. Consequently, we have decided to close the bug.
Resolution Note (6000.0.X):
This issue is identified as an edge case. We have explored various workarounds; however, they were not effective. Consequently, we have decided to close the bug.