Search Issue Tracker
Won't Fix
Votes
2
Found in
2019.4
2019.4.19f1
2020.2
2021.1
2021.2
Issue ID
1311509
Regression
No
[macOS] DLL inside a custom plugin cannot be found when using a ".framework" extension
How to reproduce:
1. Open the attached project's Scene labeled "BasicTest"
2. Enter the Play Mode
3. Inspect the Console Window
Expected result: No errors are thrown
Actual result: "DllNotFoundException" error is thrown
Reproducible with: 2019.4.20f1, 2020.2.4f1, 2021.1.0b7, 2021.2.0a5
Couldn't test with 2018.4.32f1 (Package references breaks when downgrading)
Note: ".framework" plugin is missing Standalone Platform settings when viewed in the Plugin Inspector
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2021.2.X):
Unfortunately, the format of framework bundles does not lend itself well to being used in the editor. Framework bundles rely heavily on symlinks, and Unity does not preserve symlinks when importing assets. This leads to duplicate files and incorrect dependencies in the framework executable. Using the entire framework package also causes the build project to have irrelevant items like header files.
Repackaging custom frameworks as bundles is a possible route for those needing to use binaries provided this way.