Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X
Votes
2
Found in
2019.1.0a10
2019.1.0a11
Issue ID
1106120
Regression
Yes
[Asset Importer] "Projectsettings.asset type mismatch" exception thrown when importing a project from asset store or collab.
"Projectsettings.asset type mismatch" exception thrown when importing a project from asset store or collab in 2019.1.0a10.
Steps to reproduce:
1) Open "[Mobile]Touch Input and Keyboards" project from Collab in 2019.1.0a10.
OR Alternatively,
1) Create new project in 2019.1.0a10.
2) Import 2d platformer (https://assetstore.unity.com/packages/essentials/tutorial-projects/2d-platformer-11228) from asset store .
Actual result: "Projectsettings.asset type mismatch" exception thrown in console.
Expected result: No error appears in the console.
Reproducible in: 2019.1.0a11, 2019.1.0a10
Working fine in: 2019.1.0a9, 2018.3.0f1
Note: Happens every time when downloading a project from Collab and majority of times when importing from Asset store.
Stack trace:
Unity failed to read signed 32 bit int at line 162 of 'projectsettings/projectsettings.asset' due to type mismatch. This problem occurs when a member field in the script has changed and Unity is attempting to load data with the old format, or when the data is corrupt.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Add comment