Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.3.0f3
Issue ID
983225
Regression
No
Plugins not copied to the Standalone Plugin folder when they are marked to be included in build
Steps to reproduce:
1. Create new Unity project
1. Import attached "dummy.dll" file for Windows or "MacURI.bundle" file for MacOS
2. Select imported plugin (make sure Any Platform is disabled and Include Platforms Editor and Standalone are enabled in Import settings)
3. Disable all checkboxes in PC, Mac and Linux Standalone Platform settings (x86 and x86_x64 for Windows, x64 for MacOS) and Apply
4. Disable Standalone and Apply
5. Enable Standalone and Apply
6. Go to File->Build Settings and build standalone player
8. Check included plugins in build (Build_Data/Plugins for Windows, Contents/Plugins for MacOS)
Expected results:
Plugins that were specified to be included in Standalone are copied to the Plugins folder in Standalone build
Actual results:
Plugin is not copied to the Plugins folder in Standalone build
Reproduced in: 2018.2.0a3, 2018.1.0b10, 2017.3.1p3, 2017.2.2f1, 2017.1.3p2, 2017.1.0a1
Workaround:
-Disable all checkboxes in PC, Mac and Linux Standalone Platform settings and Apply
-Enable all checkboxes in PC, Mac and Linux Standalone Platform settings and Apply
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Add comment