xDoc errors

Solved4.56K viewsxDoc


I’m trying to use xdoc in my project, but I am in trouble.
When starting the scene, the following error occurs.
Please let me know if you know how to deal with it.

NullReferenceException: (null)
UnityEditor.SerializedObject..ctor (UnityEngine.Object[] objs, UnityEngine.Object context) (at C:/buildslave/unity/build/artifacts/generated/common/editor/SerializedPropertyBindings.gen.cs:87)
UnityEditor.Editor.GetSerializedObjectInternal () (at C:/buildslave/unity/build/artifacts/generated/common/editor/EditorBindings.gen.cs:193)
UnityEditor.Editor.get_serializedObject () (at C:/buildslave/unity/build/artifacts/generated/common/editor/EditorBindings.gen.cs:185)
xDocEditorBase.AnnotationModule.XDocAnnotationEditorBase.OnEnable ()

I am using Google translation because I am not good at English.
I’m sorry if the sentences are weird.

Question is closed for new answers.


I have a few questions, please:

1) Which Unity version are you using?
2) Is this a new or existing project?
3) Did xDoc work before and broke now suddenly?
4) As far as I understand the error happens, when you press the play button in the editor. Am I right?


Thank you for investigating!

I do not mind about this error, I will use great xdoc.
There is also the possibility of upgrading to Unity 2017.

You are busy, but you helped me.
Thank you very much.


I’d quickly like to comment on this

1) Upgrades are always risky. Especially, if your project is not small anymore and you are behind a couple of versions. You might end up with a lot of repair work. On the other hand side you would be using a better tool and get better support (because it is the actual version).

–> But never forget: always back up!!!

2) This bug seems to be a nasty one. It seems to reappear over an over again. There are reports for this and similar and related bugs from 2014, 2015, 2016, 2017. Official bug reports are opened at Unity. Unity states to have fixed them and closes the bug reports. But users claim, that the bug is still there.

So be prepared that an upgrade might not deliver the desired result.

Finally: If it was me, I would not touch a running system and concentrate on finishing the project – unless it is your policy / habit / process to upgrade regularly. Which is a good approach too, because one day you might have to upgrade and being always as up to date as possible will usually give you a smoother upgrade experience. Ultimately, it is your decision.

Last but not least: Thanks for reporting and giving feedback! Every input helps!

You are viewing 1 out of 3 answers, click here to view all answers.