Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.23f1
Votes
0
Found in
2021.3.36f1
2022.3.9f1
Issue ID
UUM-49338
Regression
No
"Assembly with name 'Unity.InternalAPIEditorBridge.005' already exists" error when using XR and aseprite packages together
Steps to reproduce:
1) In an empty Unity project, edit the Packages/manifest.json file and set its contents to the following:
{
"dependencies": {
"com.unity.2d.aseprite": "1.0.1",
"com.unity.xr.arsubsystems": "4.2.7"
}
}
2) Go back to the Unity Editor window to resolve the packages.
Expected result:
Both packages are successfully installed and usable.
Actual result:
The following errors are logged to the console:
Assembly with name 'Unity.InternalAPIEditorBridge.005' already exists (Packages/com.unity.xr.arsubsystems/Editor/InternalBridge/Unity.InternalAPIEditorBridge.005.asmdef)
Assembly with name 'Unity.InternalAPIEditorBridge.005' already exists (Packages/com.unity.2d.aseprite/Editor/Common/InternalBridge/InternalBridgeDef.asmdef)
Reproducible on:
Unity 2022.3.9f1, 2021.3.36f1
Not reproducible on:
Unity 2023.3.0a7 (or with package com.unity.xr.arsubsystems at version 5.0.2)
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 2022.3.23f1):
Fix can be found in Aseprite Importer 1.1.2.
Resolution Note (fix version 2021.3.37f1):
Fix can be found in Aseprite Importer 1.1.2.