Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.0a1
2019.1.3f1
2019.2.0a1
Issue ID
1188030
Regression
Yes
Failed file import when editing files externally
Steps to reproduce:
1. Open the user-supplied project with Unity 5.5.6f1
2. Open the scene SampleScene.
3. Open the file Assets/Localization/Book1.csv in MS Excel
4. Go back to Unity and hit play, notice the file being read in the Console window
5. Move the project to Unity 2019.1 while keeping the file Assets/Localization/Book1.csv opened in Excel.
6. Open the scene SampleScene and hit play.
7. Note the error printed in the console. (It can be expected because the file is being used)
8. Reimport the file with Excel either open or closed.
Expected: The file gets reimported successfully
Actual: The file becomes corrupted: "File couldn't be read"
Reproduced in: 2019.1.0a1, 2019.1.3f1, 2019.2.9f1,
Not reproduced in: 2017.4.33f1, 2018.4.11f1, 2019.3.0a1 (infinite on start), 2019.3.0b6, 2020.1.0a8,
Note: Seems to be fixed in 2019.3 however, I can't find any duplicates and the customer needs the fix for 2019.1 assumingly
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
- "Assertion failed on expression" errors appear when selecting specific Tile Palette GameObjects
- “CommandBuffer: built-in render texture type 3 not found while executing” warning is displayed in URP project
- Player build logs a "material with shader doesn't have a '_MainTex' property" error when instantiating a specific amount of specific prefabs
- The LayerMask parameter is ignored when using Physics2D.GetRayIntersection method
- The Tilemap GameObject causes other Tilemap GameObjects to become invisible when its “Mask Interaction” is set to “Visible Inside Mask”
This is a duplicate of issue #1037669