Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2019.1.0a11
Issue ID
1106254
Regression
Yes
Opening/modifying a script in a Code Editor prevents a bug report from being sendable until the Code Editor is closed
Steps to reproduce:
1. Create a new project
2. Create a new script
3. Open it in Visual Studio
4. Try to submit a bug report
Expected result: bug gets packed and submitted normally
Actual result: "Error occurred while creating an archive. Error code: file read failed"
Reproduced on 2019.1.0a11, 2019.1.0b9, 2019.2.0a1 and 2019.2.0a9 on Visual Studio on Windows
Not reproduced on 2019.1.0a1 2019.1.0a10 OR 2019.1.0a11 on macOS/Visual Studio
Notes:
- Bug report becomes sendable if Visual Studio is closed
- Issue does not occur if a newly created file is not opened in VS
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a11
Backported to: 2019.1.0f2, 2019.2.0a13