Search Issue Tracker

Fixed in 2018.1.X

Fixed in 2017.4.X, 2018.2.X



Found in



Issue ID




[OSX] Unity Editor fails to build project when Performance Reporting is enabled

Cloud Diagnostics


To reproduce:

1. Download attached project "" and open in Unity
2. Open "test" scene
3. Go to the Services window
4. Enable "Performance Reporting"
5. Build & Run project

Expected Result: UnityEditor should successfully build project and run it
Actual Result: Unity Editor fails to build the project and spams errors to Console:

"Assets/GenerateException.cs(7,13): warning CS0649: Field `GenerateException.Null' is never assigned to, and will always have its default value `null’"

"WebException: The remote server returned an error: (403) Forbidden.
System.Net.HttpWebRequest.CheckFinalStatus (System.Net.WebAsyncResult result)
System.Net.HttpWebRequest.SetResponseData (System.Net.WebConnectionData data)

"Error building Player: WebException: The remote server returned an error: (403) Forbidden."

"Build completed with a result of ‘Failed’

"UnityEditor.BuildPlayerWindow+BuildMethodException: 2 errors
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (BuildPlayerOptions options) [0x0020e] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:181
at UnityEditor.BuildPlayerWindow.CallBuildMethods (Boolean askForBuildLocation, BuildOptions defaultBuildOptions) [0x00065] in /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:88

"Assets/GenerateException.cs(7,13): warning CS0649: Field `GenerateException.Null' is never assigned to, and will always have its default value `null’"

- This issue appears only on OSX
- Using .NET 3.5

Reproduced on Unity 2017.3.0a2, 2017.3.0f3 and 2018.1.0b1
Not reproduced on Unity 2017.3.0a1
Regression on Unity 2017.3.0a2

Comments (19)

  1. joniwalkerkiy

    Apr 15, 2021 08:06

  2. rochbordan11

    Aug 18, 2020 09:41!/!/!/;area=summary;u=95582;area=summary;u=349835;area=summary;u=1120!/;u=31553*!/;area=summary;u=4060;u=30513*;area=index;sa=settings;u=31558;d4ec488=4cb7fa5319cc4fee626ae7806b0779b5;u=31579;u=4053;area=summary;u=4059

  3. cozyurt_unity

    Jul 13, 2020 17:23

    kedi ve köpek mamaları kedi kumu çeşitleri

  4. iamabdurrehman

    Jul 03, 2019 07:55

    Just Login With Unity .. Error will be resolve.

  5. JunaidGhani

    Feb 12, 2019 06:37

    Unity 2017.2.0f3
    .NET FrameWork 3.5

    I was able to fix this just by signing out, restarting Unity and opening same project, I was auto logged in and build was fine! Hope it may help someone.

  6. pro_psg

    Aug 30, 2018 10:56

    Issue reproducible on 2017.1.2p4

  7. ZDestructor

    May 06, 2018 20:26

    I had a similar error, but it was because I was not signed in.

    I had previously pressed "work offline" when starting Unity, and never signed back in, which caused my build to fail since performance reporting was enabled. I checked the Services tab and found that it said "Not signed in", so I signed in, and the next build completed successfully.

  8. PNordlund

    Apr 16, 2018 06:35

    Given that 2018.1 is still in beta, 2018.2 with the fix is months away. Would expect to see the fix in 2018.1 as well.

  9. luisforque

    Mar 08, 2018 20:02

    I have this same problem in Windows, trying an Android build. Disabling the performance reporting fixes the build.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.