Requesting Assistance on System.Environment.FailFast Error after Upgrading from 2018.30f2

Unity Engine
1

Hi All,

I have just upgraded my project from Unity version 2018.30f2 to Unity 2019.2.15f1 and am now receiving the following error message upon running any scene and cannot figure out what is causing it.

Is anyone able to assist with this?

Here are the error details from the console:

NotImplementedException: The method or operation is not implemented.
System.Environment.FailFast (System.String message) (at <567df3e0919241ba98db88bec4c6696f>:0)
.‪‫‮‏‪‫‬‭‎‪‪‫‮‭‫‌‭‏‍‭‌‍‎‎‪‮ (System.String ) (at :0)
.‫‬‫‍‫‬‮‎‬‎‌‪‫‌‎‬‌‌‭‪‎‫‎‍‪‬‬‮ (System.Object ) (at :0)
System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) (at <567df3e0919241ba98db88bec4c6696f>:0)
System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) (at <567df3e0919241ba98db88bec4c6696f>:0)
System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) (at <567df3e0919241ba98db88bec4c6696f>:0)
System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) (at <567df3e0919241ba98db88bec4c6696f>:0)
System.Threading.ThreadHelper.ThreadStart (System.Object obj) (at <567df3e0919241ba98db88bec4c6696f>:0)
UnityEngine.UnhandledExceptionHandler:m__0(Object, UnhandledExceptionEventArgs) (at C:/buildslave/unity/build/Runtime/Export/Scripting/UnhandledExceptionHandler.bindings.cs:46)

Many thanks in advance for any advice on this.

Kind regards,

John

2

Hey there John, if you haven’t already, please submit a bug report so that we can investigate this further for you - you can find the process detailed here: Unity QA: Building quality with passion

3

Many thanks for your reply TreyK-47. I will see what I can do with the debugging tools mentioned in the link you have kindly provided and try to resolve or replicate the error.