"Could not extract GUID in text file projectsettings/projectsettings.asset at line 44" @ HostView

Could not extract GUID in text file projectsettings/projectsettings.asset at line 44
UnityEditor.HostView:OnGUI()

This happens twice whenever I build, and other random occurrences I'm fairly certain I've seen it.

It's an error, but double clicking does nothing and not sure what extracting GUID is supposed to actually do.

Anyone seen this before?

 

ye. For me, this is a constant error. I've setup a background for splash screen, and this error is related to it. (as I see in settings text file, the background item's GUID is like 00000000000000000000000000000000000000000.

 

Ah - I have a splash background, too! There must be tons of people with this error, then (or ours are corrupt?). Did you ever find a way to fix it? Maybe re-set the background? hmm..

 

I have same problem but now I cannot even get a build to work by changing the fileid to 0. It used to work but no more. I had sent out many publisher emails this week with a demo of my game in WebGL. Well unity broke the remotesettings plugin I had installed sometime after and now I've probably blown my chances because I only noticed a few days later. Then I updated the remote settings plugin which had the fix for webgl but now I can't do a build because of this GUID bug. I have never been so stressed and angry at Unity in my life. All they care about is rushing through version after version and I blame the managers at the top. Getting sick and tired of the bugs and lack of QA. If you go on to the issues tracker you will see that this problem was reported a long long time ago but unity just marked it as "fixed". Had enough

 

I have been developing with Unity for two years now. And you know what, I noticed this, too. For MANY bugs that I currently have, they were mysteriously "fixed". Even commented it's not fixed, it never reopens. If you create a ticket saying it's not fixed, it's still never reopened.

You think that's bad? You know UNET, Unity's mplayer? I was sold by their epic marketing and promises. Almost a year later, still no docs, no support, no demo, nothing working from what I've read, and no QA except to appear once per 6 months to apologize. They "released out of beta" over a year ago.

5.5 to 5.6? They broke FB standalone *completely*. I reported it in beta, and they still brought it to release without even bothering to test it. They implemented FB Gameroom and forgot to test it with standalone and just swept it under the carpet, again, much like these mysteriously "fixed" bugs.

Collab? Awesome devs, terrible upper mgmt that forces them to rush out of beta. Sooo many critical bugs. Again, just swept under the carpet. Or making us pay for a new unstable version to get a bug fix or two. We left collab and 1/2 our Unity issues poofed away.

So many bug reports -- I should be getting paid for how much time I've spent reporting detailed bugs. Even then, still not fixed -- they're focusing on fluff features instead of fixing bugs, just like UNET. That's the pattern I've noticed over the past 2 years:

Implemented, then abandoned. Such a shame when there are so many competitors out there now

 

I've been saying this for a long time. The management are short sighted. About a year ago the big statement was "You spoke and we heard. We are now focused on fixing more bugs per patch release." Well that quickly went the way of the dodo because all year I have been struggling with an increase of bugs in all of my games. You report them and you may be lucky to get unity to look at it within 6 months. Some of them totally ruined my games.

But in regards to this problem, last night I spent many many hours trying to figure it out. I found a solution that may help you. Basically go into your editor settings and change the serialization from text to mixed and then build your game. Remember to turn it back to text before you commit anything to you git because I do not know what mixed would do there.

Hope it helps and I hope the unity management gets a clean out and some real tech savvy managers take their place (we the customers can see what is going on).

 

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.

 

This still randomly resets even a year later ;( The above workaround works fine, but god it happens so often~

@ Unity- please fix this bug. Existing features matter :/