Search Issue Tracker
Fixed in 5.3.5
Votes
2
Found in
5.0.0f4
Issue ID
703290
Regression
No
[Build] Building in batchmode fails for first time after removing file from project
In batchmode after removing file, project building only succeed after second time.
1. Clone project from:
https://github.com/Brantone/unity-delete-script-bug
OR
https://github.com/davehampson/unity-delete-script-bug
OR
Just download "unity-delete-script-bug.zip" if you are lazy. (Attached by Lukas)
2. Run shell script "run_test_case.sh". You should get these outputs:
...
3. Run Unity build again ... this should fail
Result: 1
Open _output/unity_editor_step_3.log and search for 'stderr'
4. Run Unity build again ... this should complete successfully
Result: 0
...
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Lex3425
Apr 25, 2020 11:23
Quite interesting to think about how this one bug has evolved that functioning and the performance over the past five years. It is so neat to be able to look back and then know how it has evolved over time. This has made our website https://www.rapidcitydrywallcontractor.com to not experience bugs or poor functioning.
BenHymers
Oct 11, 2016 16:41
This is STILL happening in 5.4.1p4. I've adapted your example project here: https://github.com/hymerman/unity-delete-script-bug
It does seem to only happen now if the platform changes between invocations too.
Mr_Friendly
Sep 18, 2015 23:36
I'm still seeing this bug in 5.1.3f1.
asdagdsgsag
Jul 15, 2015 15:21
when this patch is applied? i trouble with this issue too!