Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
Issue ID
1021290
Regression
No
[asmdef] Script defined in an Assembly Definition can't access plugins folder files
Reproduction steps:
1. Open "Assembly Definitions and Plugins.zip" project
2. Open "ScriptInAssembly.cs" script
3. Uncomment the 9th line and save the script
4. Go back to Editor and after re-compile notice the error in the Console
Expected Result: The script should be able to find the "ScriptInPlugins" file when using Assembly Definitions
Actual Result: The script can't find the appropriate plugin file, because it's in an Assembly Definition
Reproduced with: 2018.2.0b2, 2018.1.0f2, 2017.4.2f2, 2017.3.2f1, 2017.3.0b1
Did not reproduce on: 2017.3.0a7, 2017.2.2p4 (Assembly Definitions were only implemented from 2017.3.0b1)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.