Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1118822
Regression
No
Script reference lost when importing .unitypackage with .dll files
Steps to reproduce:
1. Open the attached Project "ReimportReproPackage"
2. See the Inspector Window for GameObject "ColorChaningCube" (there is a Script Component attached)
3. Export the Project as a Unity Package
4. Create new Unity Project and Import the Package
5. See the Inspector Window for GameObject "ColorChaningCube" (the Script Component lost Script refference)
Expected Result: scripts are imported with the Package
Actual Result: script references are lost and Scripts are not imported with the package
Reproducible with: 2017.4.18f1, 2018.3.3f1, 2019.1.0a14, 2019.2.0a1
Note: Asset store item "DllSwitcher " is used in the Project. Scripts are restored if Assets -> Reimport All is called.
-
Resolution Note:
Interdependent .dlls have to be in the same folder for this to work.
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
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
This is a duplicate of issue #696013