Search Issue Tracker
By Design
Votes
0
Found in
2022.3.5f1
Issue ID
UUM-43933
Regression
No
Assembly Reference to a specific DLL is lost when importing a custom package into another project
Reproduction steps:
1. Open the attached “ASDQWE” project
2. In the Project Window, right-click the “Assets/ISI Lab” folder and select “Export Package…”
3. In the Exporting Package Window, press the “Export…” Button
4. In the Export Package… Window, select a project to export the package into, name the package, and press the “Save” Button
5. Open the project that the package was imported into
6. In the Project Window, double-click the package to extract it
7. In the Import Unity Package Window, press the “Import” Button
8. In the Project Window, select “Assets/ISI Lab/LBS/LBS.asmdef” Assembly Definition Asset
9. In the Inspector Window, observe the Assembly References
Expected result: “Newtsoft.json.dll" is still referenced
Actual result: “Newtsoft.json.dll" reference is lost
Reproducible with: 2022.3.5f1
Could not test with: 2021.3.28f1 (two “error CS0246: The type or namespace name 'IntegerField' could not be found” errors), 2023.1.5f1, 2023.2.0b1 (The Project Window displays no Assets)
Reproducible on: Intel macOS 13.4.1
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note:
The project provided here has a dependency on UPM package `com.unity.nuget.newtonsoft-json`. Unfortunately asset store packages (which is the kind of package you obtain when exporting a directory) don't have any notion of package dependencies, so they won't be able to trigger the installation of newtonsoft.json UPM package in the destination project.
As a workaround, please instruct your users to add the newtonsoft package to their project.