Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.8f1
2022.1.12f1
2022.2.0b4
2023.1.0a4
Issue ID
UUM-11965
Regression
No
Cannot build projects when installing custom packages with names ending in '.framework'
h5. Repro
1. Open the attached project “PackageBub_10775.zip“
2. Open the Package Manager (Window > Package Manager)
3. Click on the plus button in the top left of the Package Manager Window
4. Click “Add package from disk…“ and select the attached “package.json“ file
5. Build And Run the project (File > Build And Run)
h5. Expected result
Project is built
h5. Actual result
Project isn’t built and errors appear in the Console
h5. Workaround
Rename package by other suffix than .framework
h5. Environment
Reproducible with: 2021.3.8f1, 2022.1.12f1, 2022.2.0b4, 2023.1.0a4
Can’t test with: 2020.3.37f1 (Errors in the Console)
Reproducible on: macOS (12.3.1)
h5. Note
Also, errors in the Console when the selected Target platform is macOS and trying to build
Comments (1)
-
Alex_Bo
Feb 14, 2023 10:15
I have the same issue on Windows with Unity 2021.3.18 when building for Android
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
- "ShaderGraph" misses a space in the "Project Settings" section
- UI Builder inspector’s checkbox fields can be activated when clicking anywhere in the value field
- Unity icon is poorly visible in the "Build Profiles" window when "Dark" editor theme is selected
- UI Toolkit Transition Animation is ignored when background-size property has a starting value of 0
- Error "Assertion failed on expression: 'i->previewArtifactID == found->second.previewArtifactID'" is present when creating Render Texture
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.