Search Issue Tracker
Active
Under Consideration for 2022.3.X, 2023.2.X
Votes
1
Found in
2022.3.3f1
2023.1.2f1
2023.2.0a21
2023.3.0a3
6000.0.0b11
Issue ID
UUM-40830
Regression
Yes
"Import Error Code: (4)" warnings are infinitely thrown when selecting local packages modified JSON file
Reproduction steps:
1. Open the attached “ASDQWE” project
2. In the Project Window, select “Packages/TestPackage/package.json” asset
3. In the Inspector Window, modify any property inside the “Information” section
4. Observe the Console Window
Expected result: No warning is displayed
Actual result: Identical “Import Error Code: (4)” warnings are thrown infinitely
Reproducible with: 2022.2.13f1, 2022.3.3f1, 2023.1.2f1, 2023.2.0a21
Not reproducible with: 2021.3.27f1, 2022.2.12f1
Reproducible on: Intel MacOS 13.4
Not reproduceable on: Windows 10 22H2, Intel MacOS 13.3.1
Note: For the reproduction to occur, sometimes changing several fields is required
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
- Render Objects Renderer Feature are not writing to the Depth Buffer when Write Depth is enabled
- Field names under "Anchors" in the RectTransform Component don't get focused when "tabbing" through the fields
- Project Browser's Search by Type stops working after importing Assets into a Project and searching for Types "In Assets" with Search Engines Project Preference Settings set to Advanced
- The Particle System Trail module creates Trails with a lighter coloring than the particles when the Color Space is set to Linear
- Crash on "in __pthread_kill" when running the built application that has UNITY_EDITOR scripting symbol in conditional compilation
djhatvr
Dec 27, 2023 03:52
I just resolved my own Infinite "Import Error Code: (4) issue.
However, mine was with a package that was added with Git URL
Also, I'm on Windows
In my case I had 2 Assembly Def files with the same name in the inspector.
After I changed the names it worked fine.