Search Issue Tracker
Not Reproducible
Votes
6
Found in
2018.1.0a3
2018.3.0a1
2018.3.9f1
2019.1.0a1
2019.2.0a1
Issue ID
1145209
Regression
Yes
Error is thrown "Cancelling DisplayDialog" when Saving Microsoft office files that are opened from Unity
Steps to reproduce:
1. Open user's attached project "ExcelImport.zip"
2. Navigate to Project -> Assets and open Test.xls with Microsoft Excel
3. Overwrite the file on Excel with Ctrl + S
4. Return to Unity
5. Observe the error message in the console
Expected results: No errors are displayed after saving Microsoft office files
Actual results: Error is thrown after saving Microsoft office files "Cancelling DisplayDialog because it was run from a thread that is not the main thread: Opening file failed Opening file"
Reproducible with: 2018.1.0a3, 2018.3.13f1, 2019.1.0f2, 2019.2.0a11
Not Reproducible with: 2017.4.25.f1, 2018.1.0a2
-
andyz
May 10, 2020 13:31
Huge issue in 2018 LTS, come on! As ALEXEES says there are major VS to Unity bugs that can occur
-
Krishna_psk
Feb 02, 2020 16:36
im facing the same issue as above. the file goes missing in the inspector. is there a solution for this?? will this effect the play in the apk??
-
zhbjvd
Sep 20, 2019 07:21
This is happening for .cs files too. It happens when there are multiple compile errors in the same file.
Cancelling DisplayDialog because it was run from a thread that is not the main thread: Opening file failed Opening file *.cs: The system cannot find the file specified.
-
Alexees
Jul 21, 2019 20:27
I would like to add 2018.4.2f1.
Whenever that happens, the script that was open with VS goes missing. It shows up with a blank page icon and I have to reimport it for Unity to recognize again.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Does not reproduce in the newest versions