Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.7f1
2018.4.0a1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1140982
Regression
No
Serialized references are reported as null when queuing up multiple builds from CLI
How to reproduce:
1. In the attached project folder, open "build.ps1" PowerShell script and set the "UNITY_EXE" path to your "Unity.exe" file
2. Make sure that the specified Unity installation has IL2CPP installed
3. Run the "build.ps1" script
4. Check the generated "build-editor.log" file
Expected results: All builds build successfully
Actual results: the first build builds successfully, all other queued builds fail because of missing serialized references
Reproducible with: 2018.4.1f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a5
Couldn't test with 2017.4 because it doesn't support IL2CPP
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Different platforms require assets to be reimported which can cause the asset to be unloaded as such with this case. The recommendation for building from command line is to launch unity using the -buildTarget option for the platform you want to build, build just that platform, then close unity and repeat for each unique platform. This ensures the state of the editor is correct for each platform build.