Search Issue Tracker
Fixed in 2017.2.X
Votes
4
Found in
5.6.1f1
Issue ID
914990
Regression
No
Invalid GUID in project settings after every build on Android
Steps to reproduce:
1. Open attached project
2. Build and run for android
-Could not extract GUID Error appears ( if error didn't appear, build and run for android again)
Error: Could not extract GUID in text file projectsettings/projectsettings.asset at line 44.
Results: Every time before building for Android you have to manually replace incorrect GUID value with 0
GUID gets set to m_SplashScreenBackgroundLandscape: {fileID: 1, guid: 00000000000000000000000000000000, type: 0}
It should be m_SplashScreenBackgroundLandscape: {fileID: 1, guid: 0, type: 0}
Reproduced with: 5.6.1p1, 2017.1.0b7
Couldn't test on 5.5 due to multiple errors (attached .png)
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
MrLucid72
Jun 16, 2018 15:15
This was found in 5.6, why isn't it patched in for 5.6?
behnam-lum
Apr 12, 2018 15:04
This is still an issue in 2017.1.2p4.
AppA11y2
Apr 09, 2018 17:57
XMAN800's comment above works for us...
"Save Scenes from the File menu, even if you haven't made any scene changes. Then "Build and Run".
behnam-lum
Apr 05, 2018 15:07
HERE IS THE SOLUTION
So the issue (at least on my side) as people mentioned above is coming from having `splashScreenBackgroundSourceLandscape` and `splashScreenBackgroundSourcePortrait` set to `{fileID: 0, guid: 000000000000000000000000000000000, type: 0}`. First confirm that you also have the same issue for the same fields. If not just look at your error message and find which field is giving you this error it should have that trail of zeros as the ID.
Now just search for `m_SplashScreenBackgroundLandscape`, `m_SplashScreenBackgroundPortrait` or just add `m_` in front of the field name that has this problem and search for it in the file. You should be able to find the correct value there, just copy and paste the value in those fields that have the problem. For example for me the correct value for `splashScreenBackgroundSourceLandscape` should have been {fileID: 21300000, guid: 2ae2e71466b7e4132a2f6e5828f57fa6, type: 3}. This should solve the issue.
Plan B
Go ahead and find the GUID of the file that is set for splash screen. You can find it in its corresponding `.meta` file. So if the file name is `splashscreen.png` you should look for `splashscreen.png.meta`. Search for that GUID in your entire project, if you are using text based YAML format for all your assets then you should be able to find a reference to that file in some other place. After you find it just copy the value which should look like the value above and paste it where the problem is coming from.
Hope it helps you all, let me know if you encounter any other issues.
FREEZX
Nov 10, 2017 14:30
Not fixed for 5.x versions.
Currently encountering it on 5.6.4f1
Amir-Ward
Oct 15, 2017 08:38
This is not fixed, what the hell unity?
xman800
Oct 12, 2017 02:46
I found a workaround -- at least for version 5.6.1f1 that I'm running: Save Scenes from the File menu, even if you haven't made any scene changes. Then "Build and Run".
FizzyJmo
Oct 06, 2017 00:36
I'm running 2017.1.1p4 and I am still seeing this issue.
Karim-Largelabs
Oct 03, 2017 12:23
Still facing it in 2017.1.1f1. Each time I want to build, I get an error, then I need to go manually change this line in ProjectSettings.asset
m_SplashScreenBackgroundLandscape: {fileID: 1, guid: 00000000000000000000000000000000, type: 0}
This is slowing us down quite a lot on the long run. A fix would be much appreciated
MrLucid72
Sep 16, 2017 13:06
"Fixed in Unity 2017.2" it should really be patched in -- this is why there's never a stable version of Unity because bugs are introduced and then instead of testing until it's stable, you hold the version hostage "if you want this bug fixed, you have to upgrade", introducing even more bugs.
Come on Unity. Give us a stable version. Just once :(