Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2020.1.2f1
2020.2
Issue ID
1275878
Regression
No
"Could not extract GUID in text file at line" error without file name when importing prefab
Reproduction steps:
1. Open new project
2. In Project window, import attached file "GUID.prefab"
3. Observe Console window
Expected result: All GUID errors are "Could not extract GUID in text file Assets/Scenes/GUID.prefab at line <...>"
Actual result: Some GUID errors are "Could not extract GUID in text file at line <...>"
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b4
Comments (2)
-
svhunt
Apr 16, 2022 02:11
It appears to still be an issue with 2021.2.14f1 at least for mac(m1/metal) when using visual scripting.
-
nixsnake
Nov 23, 2021 18:53
Got it in Visual Scripting application: Clive the Cat's 'Visual Crypting' tutorial project
Unity version: 2022.1.0a15 and 2021.2.3f1Could not extract GUID in text file UserSettings\Layouts\default-2022.dwlt at line 296.
UnityEditor.WindowLayout:LoadDefaultWindowPreferences ()Broken text PPtr. GUID 00000000000000000000000000000000 fileID 8458124308623808283 is invalid!
UnityEditor.WindowLayout:LoadDefaultWindowPreferences ()
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
- Texture displays visual artifacts and has a broken aspect ratio when it is imported in RGB 48-bit format
- Diagnostic Warning Resets When Navigating Away and Returning to Diagnostics Settings
- Checkbox Collides with Text in Shader Graph Preferences Settings
- Crash on mecanim::animation::TransformValuesFromClip when entering the Play Mode in a project with Animancer Pro v8
- Connection to Named Pipes fails when server and client are run
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a1