InvalidOperationException: Current error context error is different to requested error. about giles HOT 4 CLOSED

I've investigated further and it seems one object in particular is causing eventual problems. One of my prefabs is an empty gameObject with Pb_Meta Data Component attached. It has 3 child objects. 2 of the child objects have Mesh Filters and Mesh Renderers. The third object has a box collider and some C# monobehaviours I wrote.

I found this out by saving a level in Giles that only had this prefab. After an hour Giles was no longer able to open the .json level and gave the above crash. I'll be creating even simpler prefabs to see if I can recreate it again.

from giles.

Possibly related (probably):

http://stackoverflow.com/questions/34396039/current-error-context-error-is-different-to-requested-error-exception-in-json

from giles.

Here are two example files. Both were created with just an empty Gameobject with a child object that had the Unity Mesh Filter(cube) and Mesh Renderer. Default material. The difference between the two files are the Version=2.0.6262.37719. If you merge the fixed Version= into the Broken Version= it'll fix the Json error. Not sure what this Version thing is or how it breaks anything.

ParentChildMeshFilter_broken.json.txt
ParentChildMeshFilter_working.json.txt

from giles.

Figured it out. Turns out I was using a c# file that incremented the assembly build version a lot. Taken from here: http://xeophin.net/en/blog/2014/05/09/simple-version-numbering-unity3d

For some reason the JSON reader doesn't like it when you do that so I commented the file out and now no more of this error.

from giles.