Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.40f1
2022.3.37f1
6000.0.10f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-75880
Regression
No
Assembly Definition files .asmdef are not included when exporting package
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes” folder
3. Righ-click on “SampleScene” Scene and click Export Package…
4. Observe the Export Package dialog
Expected result: The assembly definition file ( .asmdef ) is included in the package
Actual result: The assembly definition file ( .asmdef ) is not included in the package
Reproducible with: 2021.3.40f1, 2022.3.37f1, 6000.0.10f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Comments (2)
-
Whatever560
Aug 19, 2025 08:09
As a workaround one can type "t:asmdef" in the project search bar, select them all and export.
-
Whatever560
Aug 19, 2025 08:06
Faced this issue as well. (6.1.14f1) Very problematic when trying to export a repro for a crash for example.
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
This is working as intended.
The reason the .asmdef is not included is that the dependency direction is reversed—the .asmdef depends on the script file, not the other way around. As a result, the .asmdef is not listed as a dependency when exporting a package.