Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0b5
2019.4
2020.1
2020.1.4f1
2020.2
Issue ID
1277285
Regression
Yes
Package errors are thrown when switching the build platform after updating the project from Unity 2018.4 version
How to reproduce:
1. Create a new project in Unity 2018.4.27f1 or earlier
2. Close the project and open it in unity 2019.3.0b5 or later
3. Open the Build Settings (File->Build Settings...)
4. Switch to the Nintendo Switch platform
5. Switch to the Standalone Platform
Expected results: No errors are thrown
Actual results: Errors are thrown in the Console
Reproducible with: 2019.3.0b5, 2019.4.11f1, 2020.1.6f1, 2020.2.0b3
Not reproducible with: 2018.4.27f1, 2019.3.0b4
Notes:
- Restarting Unity fixes the issue and errors disappear
- The issue does not reproduce when upgrading a project from Unity 2019.3.0a1 or later to Unity 2019.3.0b5 or later
- The issue does not reproduce when upgrading to Unity 2018.4.27f1 or earlier
- The issue is reproducible only when switching between Nintendo Switch, PS4, or Xbox One, TVos, and Standalone platforms
- Different Unity versions and different platforms can give errors from different packages, these are the packages that can give errors:
Analytics Library
In-App Purchasing
XR Legacy Input Helpers
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1