Search Issue Tracker
Fixed
Fixed in 2023.2.4f1, 2023.3.0a18
Votes
1
Found in
2023.2.0b17
2023.3.0a13
Issue ID
UUM-55556
Regression
Yes
2 assertion errors are logged in the Console when importing the user's project with a plugin to a newly created one
Reproduction steps:
1. Create a new project in any of the 2023.2.0a17-2023.3.0a13 Unity Editor versions
2. Copy-paste the files of the user-attached “asset-test.zip“ project to the newly created project via the Windows File Explorer
3. Select “Replace the files in the destination” if prompted
Expected result: No errors are thrown in the Console
Actual result: 2 assertion errors are thrown in the Console (see below for full error messages)
Reproducible with: 2023.2.0a17, 2023.2.0b17, 2023.3.0a13
Not reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.19f1, 2023.2.0a16
Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested
Notes:
- See internal comments for the link to the PR which might be causing the issue
- The user encountered the problem after upgrading their project with a plugin to the 2023 Unity Editor stream
First error message:
”PluginImporter::GenerateAssetData should never be called. Asset path='Assets/MicrosoftGame.Config'“
Second error message:
”Assertion failed on expression: 'foundQueueIndex'“
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 2023.3.0a18):
Fixed assertion errors that occur when importing case insensitive plugins.
Resolution Note (fix version 2023.2.4f1):
Fixed assertion errors that occur when importing case insensitive plugins.